perl-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vivek Khera <kh...@kcilink.com>
Subject Re: [mp2] perl_clone takes 5 and more seconds to complete
Date Wed, 05 Nov 2003 14:37:59 GMT
>>>>> "SB" == Stas Bekman <stas@stason.org> writes:

SB> Where does this bring us? When a new request is coming in and all
SB> interpreters are busy and the pool quota is not full, a new
SB> interepreter will be cloned.  And your request will be served in
SB> 6-10 secs instead of 50msecs. Now imagine a busy webserver with no

Well, that would make for an argument to scale your hardware to match
your expectations and load.  You can't make your hardware run more
than 100% unless you switch worlds over to Star Trek...

Anyhow, why would it take so long to clone a thread?  Is perl chasing
down every single memory pointer or something?  It kind of makes you
rethink the whole 'threads are better than processes' debate if your
threads are more heavy-weight than processes ;-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org


Mime
View raw message