RE: Berkeley DB with Euphoria

new topic     » goto parent     » topic index » view thread      » older message » newer message

Robert Craig wrote:
> Andy Serpa writes:
> > Well, 1.2 GB is too big.  It is not the size so much 
> > as the speed as EDS gets slower and slower as it grows...
> 
> I recently speeded up my copy of EDS.
> It reads records twice as fast as before, and it
> inserts and deletes into huge (100,000 record)
> databases 3 times as fast. Even the released
> EDS can insert/delete many times per second
> on huge databases on a slow machine. 
> If you acquire new records via a human entering 
> data into a GUI, you'll never notice the time.
> 

I'd like to get your copy.  Possible?

I speeded up my own copy a little bit (like caching key pointers so when 
it switches tables back & forth it doesn't have to read them in every 
time) but yours sounds like a major improvement.


> But if you are starting at 1.2GB and growing 0.1 GB/month
> I'd be a bit worried about the 4GB limit. Of course
> you could consider creating several separate databases
> of 4Gb or less each.
> 

Well, it holds so many years of data and grows every month, but at the 
end of the year you can dump a years worth of data off the beginning, so 
it doesn't grow forever.

But my intention was certainly not to trash anything.  I *LIKE* EDS, I 
*LIKE* SQLite, but I'd still like to give Berkeley DB a try!  Even an 
improved EDS certainly couldn't compete with optimized C in terms of 
speed (the web site says something about 1000's of inserts a second) and 
Berkeley also has things like transaction support, etc.

Really would love your version of EDS, though, Rob.

-- Andy

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu