Re^2: Most efficient way to build output file?

It takes 3 seconds...

...on your system. He might be running this on an old Ultra 2 with 16 Kb of RAM. Who knows? Plus, this will hopefully not be the OP's last foray into perl. It's best to know what "best practices" are in the general case.

thor

Comment on Re^2: Most efficient way to build output file?

Replies are listed 'Best First'.
Re^3: Most efficient way to build output file? by BrowserUk (Patriarch) on Jul 27, 2004 at 03:36 UTC
Point taken. Although, with 16kb of ram it's doubtful that perl would run, never mind have enough room for extra buffering :) I wasn't trying to be dismissive. If he genuinely has a problem with the performance he is seeing--he's deal with a slow NFS or a network share or similar--then that information might prompt a better alternative. Hence my question. I could have made that clearer. Examine what is said, not who speaks. "Efficiency is intelligent laziness." -David Dunham "Think for yourself!" - Abigail "Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon	[reply]

Replies are listed 'Best First'.

Re^3: Most efficient way to build output file?
by BrowserUk (Patriarch) on Jul 27, 2004 at 03:36 UTC

Point taken. Although, with 16kb of ram it's doubtful that perl would run, never mind have enough room for extra buffering :)

I wasn't trying to be dismissive. If he genuinely has a problem with the performance he is seeing--he's deal with a slow NFS or a network share or similar--then that information might prompt a better alternative. Hence my question.

I could have made that clearer.

Examine what is said, not who speaks.

"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon

[reply]