[Seaside] Seaside memory consumption?

[Philippe Marschall]

2008/4/29 Andreas Raab <andreas.raab at gmx.de>:
> 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)?

Honestly this is a very hard question that probably only marketing
developments can answer seriously (JEE is twice as fast as .Net). If
have seen such numbers for no web framework. There are so many free
variables. How have active users, what session lifetime, how active
are they, do they come in bursts, how complicated is your site, what
image do you have, which VM, which GC settings, which patches, which
OS, which CPU, .... . Out of the blue I would say Seaside and Magritte
are probably the most memory hungry choices you can make. Lots of
classes, lots of objects, lots of block contexts, .... Having that
said I know of no one who has run into memory problems with Seaside /
Magritte but this means very little. In general persistence is often
bottleneck. As you run code besides it I doubt any numbers would be
applicable to you.

In general people who come up with such questions have an idea about
the load they'll face or have to support so they can write tests.

> What
> about memory consumption of Seaside apps that run for several months without
> restart (session cleanup etc)?

Session cleanup happens even without restarts. If you run the
WeakDictionary patches of Martin van Löws (I hope I got the name
right) you can override SeasidePlatformSupport class >>
#weakDictionaryOfSize: which should release sessions earlier. I have
seen images that run without troubles for months and images that have
trouble staying up for more than a few days.

Cheers
Philippe