Berin Loritsch wrote:
> > Berin, I spent several *months* finetuning the thread-pool code that was
> > used in Apache JServ 1.0 (and is still there, used in both IBM WebSphere
> > and Oracle Application Server). I remember that I got a report from
> > Alcatel that they were using it with loads up to 12000 req/sec.
>
> :) And how many *threads* running simultaneously?
If I'm not mistaken, they were more than several hundreds concurrent
requests.
> Remember, Requests/Second != cuncurrent threads
Of course.
> Apache HTTPD in it's default configuration will run up to 150 processess,
> and when there are more connections than processess, it will make further
> requests wait.
>
> 12000 req/sec translates to 12.5 ms/request with 150 processes/threads.
> It also translates to 41.6ms/request with 500 processes/threads.
>
> (In another mail I will post my formula for scaling requirements)
>
> > Guess that if you need something clean and scalable, that's the way to
> > go :)
> >
> > [I proposed this a while back but you and Peter tought it was too
> > complex.... but I still like mine more :) but I'm biased]
>
> ( Aren't we all ;P )
>
> I think the implementations we have now fit that bill--clean and scalable.
kool.
> The question remains about the ECM itself yet. I haven't had time to write
> the profiling tests yet.
I fully trust your judgement on this.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
