I am trying to concoct and script that will take a binary data stream from
tcpdump, feed it into a filter, then in another instance of wheel::run,
hexdump the data stream from the filter. The code I have come up with so
far is in the 6th entry in the "Continuous packet capture" thread. I
cannot
It is too soon to conclude that POE is the cause.
The difference in CPU time between your Python and Perl tests is
0.0002 seconds per article (user+sys). It's not a significant
difference at this scale. It could be caused by any number of low-
level variations between POE and Twisted, or P
Hi,
On Wed, Mar 25, 2009 at 11:14 PM, Chris Prather wrote:
>
> That's a big supposition to make:
>
Please understand that my original email is comparing 37 vs 18 seconds
difference (i.e. 200% speedup), so I don't really care about the
startup/shutdown time since the difference is such obvious.
On Wed, Mar 25, 2009 at 11:03 AM, howard chen wrote:
> Hello,
>
> On Wed, Mar 25, 2009 at 4:10 AM, Rocco Caputo wrote:
>>
>> time(1) includes Perl & Python startup/shutdown time, which may be
>> significant.
>>
>
> Suppose the difference is negligible.
That's a big supposition to make:
[11:12:3
Hello,
On Wed, Mar 25, 2009 at 4:10 AM, Rocco Caputo wrote:
>
> time(1) includes Perl & Python startup/shutdown time, which may be
> significant.
>
Suppose the difference is negligible.
> Your times seem to be wall clock based, which can vary based on system load,
> network conditions, and so
