Amazon Cloud even has widely installed "memcached", hat works also as httpd cache, preventing any Apache webserver and indirect Pharo Webserver from "seeing" any http/get request. So, i am NOT surprised, that any of those Pharoers doesn't want me here ... Pharo *is* dogsloooooow, Seaside nearly *unusable*. Unusable for any serious business application, unforseeable memory pumping effects, expecially in vservers with limited or even dynamically assigned memory. I will open Benchmarks later ... happy hacking! best, Guido Stepken Am 13.02.2012 17:53 schrieb "Sven Van Caekenberghe" <sven@beta9.be>:
On 13 Feb 2012, at 17:25, Guido Stepken wrote:
Hahaha! You are running Apache Server in Front, caching all I/O, leaving no load for Pharo at all, serving static webpages even.
Of course I am not: Apache 2 mod_proxy doesn't do any caching at all, it is only load balancing, but to know that you have to be able to read.
Furthermore, Apache serving static files is way faster than that, something most people know, you apparently not.
And just for the record: I am comparing Pharo with other dynamic languages for dynamically generated content.
Anyway, do you have anything useful to contribute ?