client-server speed

[Ruslan Zasukhin]

On 8/20/05 1:27 AM, "Charles Yeomans" <yeomans at desuetude.com> wrote:

> Using VServer  + client appears to run an order of magnitude more
> slowly even when both client and server are on the same machine.
> Obviously one expects a certain speed hit, but I'm wondering whether
> I'm doing some things to make it worse.  Can anyone make some generic
> suggestions to solve my generic problem?

Hi Charles,

General Rules are:

* if you going to use client/server in the internet or in other way with
slow network then you must to use only SQL way. Because

    query   -> go to server only string
    result  <- come back.

* you should do query as simple as possible.
    touch as few records as possible.

* if you know that you find MANY records, then use ServerSide cursors.



-------------
Can you use API way and Classes way with Vserver?

Actually most DBMS even do not have such option.
We provide it for vserver for 2 cases

A) you have LOCAL database in this style, so you are able fast turn it into
client/server app.

B) this style in ideal must be used only on fast intranet or local networks
such as 100 or 1000 Mbit.  Problem with API way is that objects from client
send small requests to server objects and wait for answer. In this way work
COM/CORBA actually...


--------------
By our tests, when you run client/server on the same computer it works about
2 times slower than LOCAL version. Explanation is -- sockets.

Client and Server must do extra work to write info into stream of socket and
later extract it from there.

Btw, Macho version of V4RB client must work faster than carbon, because It
will use native OS X sockets.


-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]