Rocco Caputo wrote:
On Oct 31, 2006, at 11:10, Fei Liu wrote:
Hi Guillermo
Many thanks for your response. Here are some relevant information
you might find interesting:
[file listings]
I've attached the POE work horse module in this email. I am not
sure if this is the cause of the performance issue though because
my timing
does not show that this is slowing down things.
Let me know if you need more information about this case. One of
my colleagues claims that somehow request wasn't picked up from
actual request handler after the request handler process exits.
Perl/POE spends up to 60ms in waitpid call to wait the handler
completion and then reaps the response.
I definitely need more information.
POE's waitpid() call is usually non-blocking. If you're seeing a
blocking waitpid(), it's probably because POE::Kernel is exiting.
At exit time, POE lingers to reap its child processes so they don't
become zombies.
If this is the case, it leads me to believe that you're starting
and stopping a lot of POE processes. That's probably not the best
way to use POE.
Hi Rocco, you are absolutely correct. We are starting/stopping a lot
of POE processes. This reinforces with our conclusion that this is
rather an architectural issue.
There also seems to be a second problem: Child processes are
exiting without something being delivered where it's supposed to
go. I can't really tell if this is what you mean, or what the
details are, without more information.
--Rocco Caputo - [EMAIL PROTECTED]
I'll get more information on this question, this confuses me as well
and I need to get an answer.
