[CentralOH] Read-Only Database
godber at gmail.com
Tue Nov 9 23:42:49 CET 2010
Really, was your data actually highly structured or were you trying to use
it simply as a key value store?
I would be tempted to try this:
Or yeah, if dbm covers it, I would stick with that. The simplest possible
solution. Good recommendation Catherine (congrats on your change of
On Tue, Nov 9, 2010 at 4:20 PM, Catherine Devlin <catherine.devlin at gmail.com
> On Tue, Nov 9, 2010 at 3:53 PM, Mark Erbaugh <mark at microenh.com> wrote:
>> But you're right about SQLite. That's a good general purpose choice and
>> probably sufficient. I read somewhere that trying to find the "best" Python
>> module for a given application can drive you crazy.
>> I've actually had cruddy performance from SQLite on large databases. It's
> optimized for ease of use, not speed.
> The Lore says that nothing-but-nothing beats simple key:value storage like
> dbm for raw speed - no RDBMS, no oh-so-trendy NoSQL database, nothing - and
> it sounds like your application would qualify. Have you tried your speed
> with dbm? 800k rows sounds like something it would handle easily. I've
> never heard of optimizing it for read-only but I bet you won't need to.
> - Catherine
> CentralOH mailing list
> CentralOH at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the CentralOH