On 13 February 2012 18:09, Guido Stepken <gstepken@googlemail.com> wrote:
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.
Yes! http://httpd.apache.org/docs/1.3/mod/mod_proxy.html
Even dynamically growing cache memory.
Tnx 4 your comments. When you put *real* and *direct* load on Pharo (no tricks, no apache, no nginx in front), and you can see, what i mean: Memory pumping, eating up vasts mounts of memory at even low load (use ab -n 10000 -c 1000) ...
How about *real* and *direct* load on a sport car? Ever tried to haul fuel cistern with it? How fast it goes? The answer to your issue is just one: use proper tools for solving your problems.
Ok, facts are unwanted here. Away again! :-)
Happy hacking!
Guido Stepken
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 ?
-- Best regards, Igor Stasenko.