As I recall, 8% is around the margin of error for Benchmark. (See also No More Meaningless Benchmarks!)
Also, testing the performance of this kind of operation can be heavily influenced by outside factors. Writing files is something the OS does. Are the files fragmented? Does it have to seek a long way from some file that some other program is accessing? How fast is the disk? How much of the operation is cached?
If one of them is working better for you than the other, then go that route. I can't argue with that. That said, I don't put much faith in this particular test to show what it's meant to show.
On my machine, I get more dramatic results:
Rate File2 File1 File2 233/s -- -64% File1 645/s 177% --
I wouldn't be surprised if some other monk comes along and shows results in the other direction.
In reply to Re: File::Slurp Not As Efficient As OPEN / CLOSE
by kyle
in thread File::Slurp Not As Efficient As OPEN / CLOSE
by ~~David~~
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |