[Seaside] Re: Which persistence solution to use?
boris at deepcovelabs.com
Sun May 13 19:46:06 UTC 2007
Its not just about throughout though, there's reducing thread contention (rsa auth calls take 3 seconds where vm locks up and I want other users to be less affected by this, so we spread them around X images) as well as fault tolerance (one vm goes down, others are there to let you log in again, and some users aren't affected at all). Are you against data sharing? Isn't that what GemStone is for? ;)
(Sent from a BlackBerry)
----- Original Message -----
From: seaside-bounces at lists.squeakfoundation.org <seaside-bounces at lists.squeakfoundation.org>
To: Seaside - general discussion <seaside at lists.squeakfoundation.org>
Sent: Sun May 13 12:16:24 2007
Subject: Re: [Seaside] Re: Which persistence solution to use?
On Sunday 13 May 2007 8:52 am, Philippe Marschall wrote:
> 2007/5/13, James Foster <Smalltalk at jgfoster.net>:
> > On Sunday 13 May 2007 2:43 am, Udo Schneider wrote:
> > > James Foster wrote:
> > > > Why "outside the image"? Do you need to get access to the data from
> > > > something other than Seaside?
> > >
> > > Not really. The reason is to be able to share the data between multiple
> > > running Squeak/Seaside instances.
> > Why do you need multiple instances? Is one instance unable to handle the
> > requests?
> Scaling, computer with more than one CPU/core, failover, ....
Are you answering on behalf of Udo, or are you just providing a general list
of reasons why someone might want to run multiple instances? Are you making a
distinction between "scaling" and "computer with more than one CPU/core" or
are the two reasons equivalent? How many pages per second are your serving
such that one instance is inadequate?
Seaside mailing list
Seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside