Re: Most time spent on POE/Loop/Select.pm?

I've been having e-mail problems today.

To the original poster: It depends.  Remember: Time spent doing  
nothing (idly waiting for the next socket or timer) is attributed to  
the select() or sleep() calls in POE::Loop::Select.  Run your program  
through Devel::NYTProf, and put the resulting HTML profile report on  
the web somewhere.  Send us a link, and I'll be happy to look at it.

Better yet, send me a link to a tarballed report.  I'm looking for  
real-world profile reports for clues about optimizing POE.

Thanks!

-- 
Rocco Caputo - [email protected]


On Mar 3, 2010, at 21:26, [email protected] wrote:

> Tsz Ming WONG wrote:
>> Hello,
>>
>> On Thu, Mar 4, 2010 at 4:22 AM, [email protected] <[email protected]> wrote:
>>
>>
>>>  Without knowing what kind of profiling you are doing  
>>> ( Devel::DProf?
>>> NYTProf? )
>>>
>>
>>
>>
>> Are you able to profile POE's code using Devel::DProf without a  
>> segfault?
>   Yeah, trying to profile POE with pretty much anything else than  
> NYTProf gives you segfaults or whack results... It's just that a lot  
> of profilers are outdated but I mentioned DProf because older  
> versions of POE+perls was able to profile using it :)
>
> ~Apocalypse