From kraison at common-lisp.net  Fri Mar 18 17:31:39 2011
From: kraison at common-lisp.net (Kevin Raison)
Date: Fri, 18 Mar 2011 10:31:39 -0700
Subject: [elephant-devel] Accessing a DB from multiple processes
In-Reply-To: <50e8e4f60801250314l6ac04519ha277225a4102c786@mail.gmail.com>
References: <63396.88.73.252.27.1201258414.squirrel@mail.stardawn.org>
	<50e8e4f60801250314l6ac04519ha277225a4102c786@mail.gmail.com>
Message-ID: <4D8396FB.9020405@common-lisp.net>

I am curious about this use case for Berkeley DB;  can someone confirm
that multiple Lisp images can access a single BDB store without problems?

Thanks,
Kevin


On 01/25/2008 03:14 AM, Henrik Hjelte wrote:
> On Jan 25, 2008 11:53 AM, Leslie P. Polzer <leslie.polzer at gmx.net> wrote:
>>
>> I know that Elephant is thread-safe. Am I right in that I can also
>> open a store from separate Lisp images?
> 
> The postmodern backend is almost optimized for this use case, with its
> globally synced cache.
> 
> clsql backend works as well.
> 
> bdb backend should work... I had some problems with BDB in this use
> case, but that was some time ago so I don't know the current state.
> 
> Note that multiple image access is not tested in the elephant
> testcases. There is code for testing this in the project grand-prix on
> common-lisp.net
> 
> /Henrik
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel



From eslick at media.mit.edu  Fri Mar 18 18:17:14 2011
From: eslick at media.mit.edu (Ian Eslick)
Date: Fri, 18 Mar 2011 11:17:14 -0700
Subject: [elephant-devel] Accessing a DB from multiple processes
In-Reply-To: <4D8396FB.9020405@common-lisp.net>
References: <63396.88.73.252.27.1201258414.squirrel@mail.stardawn.org>
	<50e8e4f60801250314l6ac04519ha277225a4102c786@mail.gmail.com>
	<4D8396FB.9020405@common-lisp.net>
Message-ID: <6A1742BD-41BC-4D77-A881-4DE27D00007D@media.mit.edu>

I've done this successfully in testing and I know people who have done this in production.  Also many modern lisps use OS threads and multi-threaded apps work fine.

Cheers,
Ian

On Mar 18, 2011, at 10:31 AM, Kevin Raison wrote:

> I am curious about this use case for Berkeley DB;  can someone confirm
> that multiple Lisp images can access a single BDB store without problems?
> 
> Thanks,
> Kevin
> 
> 
> On 01/25/2008 03:14 AM, Henrik Hjelte wrote:
>> On Jan 25, 2008 11:53 AM, Leslie P. Polzer <leslie.polzer at gmx.net> wrote:
>>> 
>>> I know that Elephant is thread-safe. Am I right in that I can also
>>> open a store from separate Lisp images?
>> 
>> The postmodern backend is almost optimized for this use case, with its
>> globally synced cache.
>> 
>> clsql backend works as well.
>> 
>> bdb backend should work... I had some problems with BDB in this use
>> case, but that was some time ago so I don't know the current state.
>> 
>> Note that multiple image access is not tested in the elephant
>> testcases. There is code for testing this in the project grand-prix on
>> common-lisp.net
>> 
>> /Henrik
>> _______________________________________________
>> 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




From nikodemus at random-state.net  Tue Mar 29 05:38:16 2011
From: nikodemus at random-state.net (Nikodemus Siivola)
Date: Tue, 29 Mar 2011 08:38:16 +0300
Subject: [elephant-devel] Fwd: Elephant patch for current SBCL
In-Reply-To: <AANLkTimB9Tkq-tNahndR+C45e7PhmHn8CfDD3mBQAu=G@mail.gmail.com>
References: <AANLkTimB9Tkq-tNahndR+C45e7PhmHn8CfDD3mBQAu=G@mail.gmail.com>
Message-ID: <AANLkTik2HdVoEcp=tAAOtY-60zzJz6tL6XSpASc9OJAT@mail.gmail.com>

*cough* attached...

Cheers,

 -- Nikodemus

---------- Forwarded message ----------
From: Nikodemus Siivola <nikodemus at random-state.net>
Date: 29 March 2011 08:33
Subject: Elephant patch for current SBCL
To: quicklisp at googlegroups.com, elephant-devel at common-lisp.net,
ablumberg at common-lisp.net, rread at common-lisp.net,
ieslick at common-lisp.net


Attached a darcs diff against the 1.0 repository, which restores
buildability on recent SBCLs.

As of 1.0.46.11, various internals changed broke Elephant. I haven't
tested the attached patch very carefully, but it builds and passes
Elephant's own tests.

As near as I can tell the code I excised should never (well, for the
past few years at any rate) have been needed on SBCL.

Cheers,

?-- Nikodemus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: elephant.diff
Type: text/x-patch
Size: 3054 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/elephant-devel/attachments/20110329/3f85edc0/attachment.bin>