[elephant-devel] using one store with mutiple lisp instances

[Lukas Georgieff]

Hi,

thank you all for your comments and ideas!

> I definitely recommend the Postgres backend for your application
This seems to be the solution :-)


Best regards,

Lukas

From: eslick at media.mit.edu
Date: Thu, 5 May 2011 08:11:38 -0700
To: elephant-devel at common-lisp.net
Subject: Re: [elephant-devel] using one store with mutiple lisp instances



I definitely recommend the Postgres backend for your application.  It will be a significant amount of tricky work to get BDB replication + distributed transactions to work cleanly with Elephant.  Not worth the time / bug risks I think.  It should be trivial to migrate.
Henrik, with the caching you (or was it Alex?) put in, real world apps may perform just fine.  I suspect BDB would have a performance edge as object slot reads that miss in the cache would be satisfied with a local disk seek vs. a network transaction and remote disk seek.   I wouldn't consider distributed BDB until you hit a wall with Postgres and felt that 2x performance was a material benefit.
Ian

On May 5, 2011, at 3:10 AM, Lukas Georgieff wrote:Hi,
we have been developing our application always on top of BDB, so it would be nice to get running it in the mentioned scenario with BDB.But seems that we've to rethink and test our app with postgres!

Best regards,
Lukas


> Date: Thu, 5 May 2011 12:01:40 +0200
> From: henrik at evahjelte.com
> To: elephant-devel at common-lisp.net
> Subject: Re: [elephant-devel] using one store with mutiple lisp instances
> 
> > Has anybody of you any idea or clue that could help us to use elephant with
> > Berkeley DB in the mentioned scenario, maybe an additional framework, etc.
> > that could handle the locking of the shared db?
> >
> 
> I am curious why the postgres backend is so unpopular. As far as I
> know there is no real data to support that it is slow in "real world"
> applications. Just running the testcases and measuring total time is
> not a very good performance test. It also has caching mechanisms that
> work in multi-process applications. For an application running on
> several computer is think network performance might be a bottleneck,
> why should berkeley db have an edge in that case?
> 
> /Henrik Hjelte
> 
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel
_______________________________________________
elephant-devel site list
elephant-devel at common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel

_______________________________________________
elephant-devel site list
elephant-devel at common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/elephant-devel/attachments/20110505/c3e9b149/attachment.html>