<html><head><base href="x-msg://2440/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">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.<div><br></div><div>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.</div><div><br></div><div>Ian<br><div><br><div><div>On May 5, 2011, at 3:10 AM, Lukas Georgieff wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div class="hmmessage" style="font-size: 10pt; font-family: Tahoma; ">Hi,<div><br></div><div>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.</div><div>But seems that we've to rethink and test our app with postgres!</div><div><br></div><div><br></div><div>Best regards,</div><div><br></div><div>Lukas</div><div><br></div><div><br><br>> Date: Thu, 5 May 2011 12:01:40 +0200<br>> From:<span class="Apple-converted-space"> </span><a href="mailto:henrik@evahjelte.com">henrik@evahjelte.com</a><br>> To:<span class="Apple-converted-space"> </span><a href="mailto:elephant-devel@common-lisp.net">elephant-devel@common-lisp.net</a><br>> Subject: Re: [elephant-devel] using one store with mutiple lisp instances<br>><span class="Apple-converted-space"> </span><br>> > Has anybody of you any idea or clue that could help us to use elephant with<br>> > Berkeley DB in the mentioned scenario, maybe an additional framework, etc.<br>> > that could handle the locking of the shared db?<br>> ><br>><span class="Apple-converted-space"> </span><br>> I am curious why the postgres backend is so unpopular. As far as I<br>> know there is no real data to support that it is slow in "real world"<br>> applications. Just running the testcases and measuring total time is<br>> not a very good performance test. It also has caching mechanisms that<br>> work in multi-process applications. For an application running on<br>> several computer is think network performance might be a bottleneck,<br>> why should berkeley db have an edge in that case?<br>><span class="Apple-converted-space"> </span><br>> /Henrik Hjelte<br>><span class="Apple-converted-space"> </span><br>> _______________________________________________<br>> elephant-devel site list<br>><span class="Apple-converted-space"> </span><a href="mailto:elephant-devel@common-lisp.net">elephant-devel@common-lisp.net</a><br>><span class="Apple-converted-space"> </span><a href="http://common-lisp.net/mailman/listinfo/elephant-devel">http://common-lisp.net/mailman/listinfo/elephant-devel</a><br></div>_______________________________________________<br>elephant-devel site list<br><a href="mailto:elephant-devel@common-lisp.net">elephant-devel@common-lisp.net</a><br><a href="http://common-lisp.net/mailman/listinfo/elephant-devel">http://common-lisp.net/mailman/listinfo/elephant-devel</a></div></span></blockquote></div><br></div></div></body></html>