On Jul 29, 2011, at 11:06 AM, Lukas Renggli wrote:
Ok, problem solved. All server adaptors work now.
A little benchmark for 500 requests (concurrency level 10):
1. Zinc -- 2073.80 [Kbytes/sec] received 2. Kom -- 1857.66 [Kbytes/sec] received 3. Swzoo -- 1662.48 [Kbytes/sec] received
Zinc can nicely play out the keep-alive. Kom doesn't support keep-alive. With Swazoo a lot of requests fail if keep-alive is enabled (so I disabled it). Details in the attachment.
what is keep-alive?
Glad that we have Zinc as the default server now :-)
Yes We are waiting for SSL now :) And a little piece of text for the success story because this is nice to hear that pharo is also good for server side only manipulation.
Lukas
On 29 July 2011 07:51, Philippe Marschall <kustos@gmx.net> wrote:
On 29.07.2011 07:46, Philippe Marschall wrote:
On 28.07.2011 22:34, Sven Van Caekenberghe wrote:
On 28 Jul 2011, at 21:11, Lukas Renggli wrote:
I cannot reproduce, but one thing that seems strange with Zinc is that when I stop the server it actually takes 10 to 20 seconds for the site to stop responding ... :-/
Lukas
-- Lukas Renggli www.lukas-renggli.ch
I tried build #651 of seaside3-zinc and that seems to work OK now.
When I start the image, there is another issue though: CPU usage goes to 100% seemingly to a process stuck in ScrollBar>>#animateValue:duration: (priority 40, almost no stack trace, just 2 frames). Killing it brought the CPU usage to normal levels and seemed OK.
Killing that process also fixes Swazoo.
And Kom as well.
Cheers Philippe
-- Lukas Renggli www.lukas-renggli.ch