<br><br>Am Donnerstag, 17. November 2011 schrieb Sven Van Caekenberghe <<a href="mailto:sven@beta9.be">sven@beta9.be</a>>:<br>> Marten,<br>><br>> On 17 Nov 2011, at 00:05, Marten Feldtmann wrote:<br>><br>
>> I posted some info how to crash the newest Pharo with Seaside under heavy traffic.<br>>> Just do not know, where to leave that information:<br>>><br>>><br>>> <a href="http://schrievkrom.wordpress.com/2011/11/16/stress-test-for-seaside/">http://schrievkrom.wordpress.com/2011/11/16/stress-test-for-seaside/</a><br>
><br>> I already saw your blog post about this and thought of leaving a comment.<br>><br>> It is tempting and seems to make sense to do this kind of benchmark or load testing. I have been there myself.<br>><br>
> However, benchmarking Seaside is difficult (you are essentially testing session creation speed).<br>> Actual performance depends on many factors such as the adaptor, image, vm and OS being used.<br>><br>> Please search the Seaside and/or Pharo mailing lists for more information.<br>
><br>> You have to believe that it is possible to get good real life production performance, it is sometimes just a bit more difficult than starting an image and hitting it hard.<br>><br><br>There's the Seaside-Benchmark package which has different test for stressing the adapters and the rendering canvas. While not close to real world they help to stress the code.<br>
<br>Philippe