PDA

View Full Version : Pervasive Client Cache? And slow performance



Pieter van Dieren
1-Dec-2005, 12:54 AM
It's me again. :-)

I'm a bit confused here.
The Connectivity Kit documentation recommends me (on page 20) to turn off
the Pervasive Client Cache. So I did.
But the whitepaper "How to syccessfully Install Pervasive.SQL for DataFlex"
that comes with the CK as well, tells me to experiment with the client cache
and do some tests to see what gives the best performance.

Erm... So, should it be on or off?

Another problem I have:
I've converted a program to Pervasive.
So I did a simple comparison: I took a database containing about 35000
records, and made a query that writes the data to an ascii file.

With the embedded dataflex database, it takes about 1 minute.
With the pervasive database, this takes about 2.5 minutes!
I've done the test several times with the same results.
Another test with a report is a lot slower in Pervasive as well.

Server: Pervasive.SQL 9.1 SP1 in Windows 2003 server
Client: Windows XP

What have I done wrong?

--

Pieter

Anders Öhrt
1-Dec-2005, 03:51 AM
> Erm... So, should it be on or off?

Off. And, delete (or rename) the cache engine too, (w3dbsmgr.exe).

Basically, client caching doesn't work. If you only read, and don't mind
stale data, you _can_ use it, but is most cases it simple doesn't work.


> With the embedded dataflex database, it takes about 1 minute.
> With the pervasive database, this takes about 2.5 minutes!

If you were the only reader (which I assume since it was a test), pervasive
will be slower. As soon as you all some real clients, pervasive will be
faster.

// Anders

Pieter van Dieren
1-Dec-2005, 04:45 AM
Anders,

> If you were the only reader (which I assume since it was a test),
> pervasive will be slower. As soon as you all some real clients, pervasive
> will be faster.

Grumble..
Now you mention it, I remember I read about it: Test in a multi-user
environment.

Thanks for your response.

--

Pieter

Jim Albright
12-Mar-2010, 11:00 AM
I was seeing slowness in PSQL V10.2 with delays in saving/deleting of up to 45 seconds. I read this thread and turned off the wbexec32.exe (the client cache engine for v10.2), renamed it to prevent reload, and the problems went away immediately.

Thanks for the tip.