On Jun 15, 9:34 am, Oveek <mov...@gmail.com> wrote:
> 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.

One of the things I like about sqlite is the tidiness of it: It's just
that one file, no DB server to worry about. On the other hand, you
don't get the flexibility and rigor that some of the servers provide.

> 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.

Excellent.

> 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.

One thing to keep in mind is that there may be scheme adjustments that
make sense. May be missing an index in a crucial place. Or some of the
SQL being generated could be entirely lame.

We may wish to add a connection pool size configuration item to the
server_store line when using the sql store.

I'm glad to hear that it is pretty much working for you. You've been a
huge help.

Now on to some other plugin or feature that should hopefully uncover a
bunch of bugs. Any suggestions?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To post to this group, send email to TiddlyWikiDev@googlegroups.com
To unsubscribe from this group, send email to 
tiddlywikidev+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/TiddlyWikiDev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to