On Dec 14, 2008, at 12:16 PM, Omry Yadan wrote:
>> I'd be interested to know if you still get the crash if you enable >> pooling on linux. >> > Enabling pooling seems to have resolved my situation, and I have not > seen any crashes yet (in the last 12 hours). > Quoting the ticket: > "But on Linux, you very quickly run into the following crash (all it > takes are 2 concurrent requests to the timeline):" > > since my stress test was 15 concurrent connections to the timeline > and I > had no problems, I assume this is no longer an issue. I think it's important to remember is that a connection pool's job is to reduce the connection overhead by reusing existing connections. This is important for most server based databases where this overhead can be very noticeable. But with sqlite's in-process design this benefit should be much less noticeable if it's even measurable. SQLite's Achilles' heel is concurrency. Only one active transaction is allowed at a time, regardless if the connection is "pooled" or not. So that's why I can't really understand how enabling connection pooling could on its own so clearly make all your concurrency related problems go away. / Jonas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
