On 2/19/07, Eric S. Johansson <[EMAIL PROTECTED]> wrote:
Joe Wilson wrote:
>> 2) can I use it for a message store and have it run faster than a 1
>> message per file system?
>
> What does that mean? Is "file system" a unit of time?
ack! bad sentence construction... comparing a system storing 1 message
per file (and thousands of messages total) vrs one storing messages as
blobs or text in sqlite, which is faster?
only benchmarking can tell definitively. But, if you know which file
to open, and you know where exactly it is at, probably opening the
file would be very fast. Navigating filesystem folder hierarchy does
start slowing down as the number of files increases (beyond a few
thousand), but you can circumvent that by creating a smart hierarchy
schema.
But, why bother. SQLite will store your text and allow you to get to
it plenty fast, especially if you need complicated criteria to get to
it. However, if you are getting to the message using a single, unique
criteria, a Berkeley DB hash would probably be much faster (at one
point I did some tests, and BDB beat most everything). However, you
probably have a good reason to consider a SQL db, in which case SQLite
is a great choice.
..
--
Puneet Kishor http://punkish.eidesis.org/
Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/
Open Source Geospatial Foundation http://www.osgeo.org/education/
---------------------------------------------------------------------
collaborate, communicate, compete
=====================================================================
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
