[Seaside] Re: Which persistence solution to use?

Udo Schneider Udo.Schneider at homeaddress.de
Mon May 14 07:47:16 UTC 2007

James Foster wrote:
> Why do you need multiple instances? Is one instance unable to handle the 
> requests?
# of requests is only the surface of the problem. The squeak instances 
are doing some heavy picture manipulating work in the background. 
Although this is done via C code (FFI and InterpreterPlugins) this is 
still quite slow. From first testing I'd go for 20 Sessions max per CPU 
(P4 2 Ghz). So that's the bottleneck. Hence the idea to put the DB on a 
shared NAS to keep as much CPU Power on the frontend as possible.

>>> http://seaside.gemstone.com/
>>> http://gemstonesoup.wordpress.com/
>> Saw that and was quite impressed to be honest. What about availibilty?
>> .... and pricing!
> Availability was announced as Q3 (we are aiming for ESUG).
> Pricing is "no cost" for a database under 4 GB.
Now that's very interesting. Does GS allow one to seperate into an DB 
backend and DB frontend? I mean having all the data shared in one DB and 
having the GS frontends doing the Seaside and local/temp storage stuff?



More information about the seaside mailing list