--- ArtemGr <[EMAIL PROTECTED]> wrote:
> More than the cache size i specified via "PRAGMA cache_size".
> I've expected SQLite to use that amount of memory for each database.
> Instead I should expect it to use that amount of memory multiplied by
> the number of threads. That've hit me unexpectedly; I think this
> should be mentioned somewhere.
This is not a SQLiteJDBC issue, but a general SQLite issue.
Reduce your cache_size to a very small number if you expect that many
concurrent users. The OS cache will make up for it.
Shared cache would not have helped in your case anyway. The shared
cache is only for connections created and used on the same thread.
This is not a typical J2EE/servlet database connection usage pattern.
> > SQLite is not the best solution for a high transaction volume database
> > anyway. Use postgres or mysql instead.
>
> But I'm not even using it with transactions. I just have multiple
> working threads. Every J2EE server have them.
SQLite may not be suitable for such a scenario.
Other databases handle a high number of concurrent requests better,
as they were designed for this purpose.
____________________________________________________________________________________
Looking for a deal? Find great prices on flights and hotels with Yahoo!
FareChase.
http://farechase.yahoo.com/
--~--~---------~--~----~------------~-------~--~----~
Mailing List: http://groups.google.com/group/sqlitejdbc?hl=en
To unsubscribe, send email to [EMAIL PROTECTED]
-~----------~----~----~----~------~----~------~--~---
