I have to main apps running dbisam and deployed in many customers.
App A, dbisam 4.24 b1, Delphi 6. Opens +100 files in startup, two
databases opened
App B, dbisam 4.26 b3, Delphi 2007. Opens +50 files in startup, two
databases opened

In both cases, a scenario is +/-:

file server, shared folder in a server (w2k svr, 2003 svr or a simple
XP box)
clients: XP, w2k.
LAN: GBit in mostly cases


All XP SP1, W2K clients open App A in less than 10 seconds, App B < 5
seconds. That's good.

SOME XP SP2/3 clients open App A +60 secods, when FIRST client opens
tables. Second client and others open tables in a good time.

App B runs the same, proportionally.

The key issue is: is someone has tables opened (same server or another
client or just dbsys) all machines open tables in a fast way.

But first client is very slow.

Also occurs closing tables.

The fact is not all XP SP2/3 clients are slow. I have not idea of what
combination of factors can make this.

Customers start one PC at morning the first and don't care about
problem, but is very strange, not?


Tiago Ameller
tiago put_an-a-_in_a_circle sistemasc.net
Sistema, S.C.

Tiago


Nah - its just Windows buffering.

Roy Lambert

Roy,

>Nah - its just Windows buffering.

Ok, but not all XP SP2/3 clients are doing it. And not all servers. Do
you know what registry entry is the key?

Searching this topic on the Web has no significant results ...


Tiago Ameller
tiago put_an-a-_in_a_circle sistemasc.net
Sistema, S.C.

Tiago,

<< The fact is not all XP SP2/3 clients are slow. I have not idea of what
combination of factors can make this. >>

Most likely this is simply an issue with the SMB file-sharing protocol in
Windows.  A simple way to test this is to set up the same configuration with
the ElevateDB Server and test it.

--
Tim Young
Elevate Software
www.elevatesoft.com