[Seaside] Re: Seaside memory consumption?

Andreas Raab andreas.raab at gmx.de
Tue Apr 29 15:54:08 UTC 2008

Sebastian Sastre wrote:
> 	in a case like that I most probably will consider a more decoupled so
> flexible architecture: seaside app in worker image/s, remote access to the
> inspected images.

Yes, that's one of the possible alternatives. Unfortunately, it would 
require serious additional work, which I'd really like to avoid 
initially by just running the interface out of the image in question. 
This still leaves me with the same question: Any experience with Seaside 
memory consumption anyone?

   - Andreas

> 	All can be restarted without affecting each other (too much), they can
> be in different hosts workers when fail wont affect observed image (guaranteed),
> etc.
> 	cheers,
> Sebastian Sastre
>> -----Mensaje original-----
>> De: seaside-bounces at lists.squeakfoundation.org 
>> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre 
>> de Andreas Raab
>> Enviado el: Lunes, 28 de Abril de 2008 21:22
>> Para: The Squeak Enterprise Aubergines Server - general discussion.
>> Asunto: [Seaside] Seaside memory consumption?
>> Hi -
>> I'm contemplating to use Seaside and Magritte to mock up an 
>> administrative interface for internal use but for various 
>> reasons this 
>> may have to run inside an image that does actual production work. 
>> Because the work can at times be memory intensive, I'm interested in 
>> learning more about memory consumption of Seaside and Magritte. Are 
>> there any guidelines for "reasonable" working sets of memory 
>> for Seaside 
>> (depending on load)? What about memory consumption of Seaside 
>> apps that 
>> run for several months without restart (session cleanup etc)?
>> Thanks for any insights,
>>    - Andreas
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list