Re^2: push, assign or split a file?

The reason that I put the Data::Dumper calls in was to make sure that the ARRAY was really being put into memory and not being delayed. If all of the tests had the Data::Dumper code, it should not affect the outcome.

I have now made it so that all the tests don't use Data::Dumper.

-- gam3
A picture is worth a thousand words, but takes 200K.

Comment on Re^2: push, assign or split a file?

Replies are listed 'Best First'.
Re^3: push, assign or split a file? by chromatic (Archbishop) on Jan 17, 2010 at 21:44 UTC
If all of the tests had the Data::Dumper code, it should not affect the outcome. Indeed it will; if you want to measure IO for reading, don't add IO for writing. IO is too non-deterministic at this level to benchmark accurately and appropriately. (That's even without Benchmark's flaws.)	[reply]
Re^4: push, assign or split a file? by gam3 (Curate) on Jan 18, 2010 at 11:53 UTC
chromatic there was no output. The Data::Dumper output was just being put in a scalar. -- gam3 A picture is worth a thousand words, but takes 200K.	[reply]
Re^5: push, assign or split a file? by chromatic (Archbishop) on Jan 18, 2010 at 18:17 UTC
Good point; I missed that.	[reply]