Processing flow data from a router. The script caches user information 
from a database then processes a 25-30MB flow file captured from a 
router using flow-tools. This takes about 5 minutes on a 2.4GHz pentium 
4 unloaded by any other process running at 98% utilisation 
continuously. To put this into context each flow file is only 15 
minutes worth of data and the current perl version does it in a bit 
over 2 minutes. This perl version is showing it's lack of design in a 
variety of ways including the nightmare of trying to add features it 
was never designed to support. So this was a good opportunity to 
rewrite it in ruby to make it more maintainable, etc.

While 5 minutes in within the time constraint that is on an unloaded 
machine and the machine it's destined for has other processes sharing 
the CPU.

Jeff.

On 03/02/2005, at 11:32 AM, Navindra Umanee wrote:

> jm <jeffm / ghostgun.com> wrote:
>> Agreed. By the looks of it it will put an end to those ruby are slow
>> comments (mine anyway).
>
> In what context did you find Ruby to be slow?  A website of yours?  Be
> interested to hear your experiences.
>
> Thanks,
> Navin.
>