<br><br><div class="gmail_quote">On Tue, Apr 29, 2008 at 6:55 PM, Miguel Cobá <<a href="mailto:m.coba.m@gmail.com">m.coba.m@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br><div class="gmail_quote"><div class="Ih2E3d">On Tue, Apr 29, 2008 at 2:40 PM, Andreas Raab <<a href="mailto:andreas.raab@gmx.de" target="_blank">andreas.raab@gmx.de</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>Philippe Marschall wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Honestly this is a very hard question that probably only marketing<br>
developments can answer seriously (JEE is twice as fast as .Net). If<br>
have seen such numbers for no web framework. There are so many free<br>
variables. How have active users, what session lifetime, how active<br>
are they, do they come in bursts, how complicated is your site, what<br>
image do you have, which VM, which GC settings, which patches, which<br>
OS, which CPU, .... . Out of the blue I would say Seaside and Magritte<br>
are probably the most memory hungry choices you can make. Lots of<br>
classes, lots of objects, lots of block contexts, .... Having that<br>
said I know of no one who has run into memory problems with Seaside /<br>
Magritte but this means very little. In general persistence is often<br>
bottleneck. As you run code besides it I doubt any numbers would be<br>
applicable to you.<br>
</blockquote>
<br></div>
I fully understand the number of variables in the setup so what I'm looking for is whether anyone has experimented with -say- running Seaside inside a 128MB environment for a given site and load factor and what their experiences were. For example, what does a small Pier deployment require? (IIRC, it is built on top of Magritte so this may be the closest in kind)<div>
</div></blockquote></div><div><br>I had my app running from a VPS with just 256MB RAM. Of course after the OS, apache, mysql, it lefted just 100MB or so. It was just imposible to work. So I upgraded to 512MB RAM and all was running ok for days without problems with my app. <br>
<br>but...<br><br>The image virtual memory grew and grew until took the entire remaining RAM to the point that I couldn't login with ssh. Not memory for forking a ssh procces was left. I had to restart the server to take control of it (the image didn't started automatically). I found an option for the squeakvm to limit the max memory available (it is not available because if the images need more memory it will begin to swap</div>
</div></blockquote><div><br>I meant: (it is not advisable because if the image need more memory ...<br><br>Miguel Cobá<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div> and will be slow, but men, it worked).<br>
After reboot, I was left with 350 MB free before running my image. So I started the image with<br><br>squeakvm -mmap 300m -headless deploy.image<br><br>so the squeak used at most 300 mb and the os had 50 MB for ssh logins.<br>
<br>Also, I changed Apache for lighttpd with fastcgi so to reduce the RAM comsumption.<br><font color="#888888"><br>Miguel Cobá<br> </font></div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
In general people who come up with such questions have an idea about<br>
the load they'll face or have to support so they can write tests.<br>
</blockquote>
<br></div>
Yes, I certainly do (it'd be in the range of 1-2 man-hours of use a day, basically filling in a bunch of forms and running a few reports mostly by a single user). But I'm not going to run a big test suite for something that is supposed to be a very small application. I just want to make sure I'm not going to screw up the production app by running Seaside next to it.<div>
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
What<br>
about memory consumption of Seaside apps that run for several months without<br>
restart (session cleanup etc)?<br>
</blockquote>
<br>
Session cleanup happens even without restarts. If you run the<br>
WeakDictionary patches of Martin van Löws (I hope I got the name<br>
right) you can override SeasidePlatformSupport class >><br>
#weakDictionaryOfSize: which should release sessions earlier. I have<br>
seen images that run without troubles for months and images that have<br>
trouble staying up for more than a few days.<br>
</blockquote>
<br></div>
Thanks, that's good to know, too. Where are these patches?<br>
<br>
Cheers,<div><div></div><div><br>
- Andreas<br>
_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org" target="_blank">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</div></div></blockquote></div></div><br>
</blockquote></div><br>