Re^3: slurped scalar map

The OS already does that for you. When you read from a file, you're not actually reading from the disk itself. You read from a buffer than the disk manager creates for you. So, slurp-process-slurp-process is going to be nearly as fast (or faster) as slurp-process-process-process.

My criteria for good software:

Does it work?
Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

Comment on Re^3: slurped scalar map

Replies are listed 'Best First'.
Re^4: slurped scalar map by 0xbeef (Hermit) on Jun 20, 2006 at 19:50 UTC
In principle I agree, except on one important detail. How can the OS buffer multiple small seek/read operations as effectively as when it is doing a single seek to start-of-file and performing a large sequential read of the entire content? On Unix systems the readahead buffer is continuously increased with logic something like "ok you're still reading sequentially - let me double the readahead buffer when doing the next read". Niel	[reply]

Replies are listed 'Best First'.

Re^4: slurped scalar map
by 0xbeef (Hermit) on Jun 20, 2006 at 19:50 UTC

How can the OS buffer multiple small seek/read operations as effectively as when it is doing a single seek to start-of-file and performing a large sequential read of the entire content?

On Unix systems the readahead buffer is continuously increased with logic something like "ok you're still reading sequentially - let me double the readahead buffer when doing the next read".

Niel

[reply]