Anyone!!!

Do any one know if i can use more than one pervasive servers and do
kind of loadbalancing on same database. I have a big site with 500+
users so i am little concern!!!

- Kintu

Currently Pevasive does not support load-balance clustering in the
strictest sense. There are some options though:

1) You could use the DataExchange product to distribute the database
to a second server. Your database may however be in violation to some
required database properties for full-sync DataExchange. May be
helpful though if you'd use the second server for read-only operations
or write to totally different tables. Possibly reporting or
data-mining.

2) Pervasive performance mainly depends on speed of network, amount of
memory, speed of disks (in that order). Speed of CPU is not often an
issue, certainly not if the server is dedicated to Pervasive. With
500+ users, server OS issues may become visible. Early tests clearly
showed NetWare servers were less prone to degenerating performance
under heavy load than Windows servers. Have not seen any recent tests
though, so Windows may have improved and Linux may even be better than
NetWare. So:
a) decrease or split network load
b) add memory
c) decrease OS load
d) replace disks or use a faster RAID configuration



On 14 Nov 2004 21:24:22 -0800, kintukshah (AT) yahoo (DOT) com (Kintu Shah)
wrote:


Gordon Bos
Q-RY Solutions
+31-(0)15-2564035

http://www.q-ry.nl/

Thanks Gordon,

Your tips did help.

- Kintu

It would be good to have a little more information about the
application, but yes 500 is quite possible.

Leonard

On Mon, 15 Nov 2004 11:45:18 +0100, Gordon
<grafzerk (AT) bigfoot (DOT) no.spam.please.com> wrote:

Probably not a good idea (except for data mining) because the
DataExchange product itself adds a bit of a load to the engine.
know it can do it.

a) If there are multiple data sets they can be hosted on separate
servers, otherwise you can split the "database" across servers and put
some files on one and other files on another.
b) Most OS platforms limit the amount of memory available to the
process to be 2GB. Certain MS platforms will allow 3GB with a boot
switch (search MS for "/3GB" for more information). Definitely have
that much memory in the server.
c) Definitely don't run other server processes on the same server, for
example email or other databases...
d) Definitely use fast disk (unless it all fits into memory anyway).