Hi Gilles,
On 6/20/07, Gilles Ganault <[EMAIL PROTECTED]> wrote:
At 16:49 19/06/2007 -0700, Medi Montaseri wrote:
The context is that, until now, our apps were almost used on stand-alone
hosts with only a few customers hosting the (small) SQLite database file on
a shared drive on the LAN, so performance was just fine. Now, we have a
customer whose DB file is about 50MB... and using a 10Mbps LAN, and it
takes about 8 seconds for an INSERT.
So we have to find a solution ASAP, with minimal changes to our app, at
least until we get around to rewriting the DB part so that it uses a
location-independent connector.
I would suggest that you develop a small application-specific Sqlite
server (specific to your application requirements - "specialized"),
put it on a machine and do ALL communication with it using straight
TCP-IP because Sqlite is an "embedded" database and I think your are
having problems because you're sharing it on a LAN. I think embedding
your database in an application-specific server and making your client
applications communicate with that server through TCP/IP (instead of
sharing on a LAN) would do the job.
--
Best regards,
Asif
Instead of putting an Sqlite database on a shared drive on a LAN, why don't you
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
