On Jun 14, 8:23 pm, "[email protected]" <[email protected]> wrote:
> Unfortunately the stuff that is working just fine for mysql and
> postgres is not working just fine for sqlite. sqlite has its own
> special connection pooling class because it get confused in multi-
> threaded environments. After a few requests in CherryPy, it will start
> throwing InvalidRequestError or complain about a different thread
> trying to a use a connection existing in another thread.
I may have to toss sqlite into my mix of databases to play with...I've
gotten curious about the performance of various combinations of
software "stacks". I've thought about creating a virtual machine that
mimics the specs of the test server at work, and experimenting with
various combinations of servers, python environments, and stores--see
how they compare.
> So I've done some rather baroque munging that seems to get around
> these issues, and may preserve the connection pooling, but I'm not
> sure. Check out my latest commits to both tiddlyweb and tiddlyweb-
> plugins/sqlstore.
Your 'baroque munging' is working well for me. It's a little
unfortunate that a database specific workaround is needed, but on the
other hand it's pretty amazing that so many databases are supported
transparently via sqlalchemy. When I wanted to quickly check how
things go with MySQL compared to postgres, I was able create an
instance in MySQL in less than 5 minutes.
> Thanks, let me know if the newest stuff does the right thing (even if
> differently).
The connection pool is still being reused under the new strategy. My
initial loadtesting of the default apache + postgres setup shows I
need considerable tuning. I may switch one or both of them. I'll
continue experimenting and report any other problems that crop up.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" 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/TiddlyWikiDev?hl=en
-~----------~----~----~----~------~----~------~--~---
