Re^3: Multi-threaded behavior, file handle dups and writing to a file

What throughput do you get if you do a simple: time cat filename >/dev/null on the same file?

That's your device/network IO baseline. (Assuming your null device is reasonably efficient.)

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Comment on Re^3: Multi-threaded behavior, file handle dups and writing to a file Download Code

Replies are listed 'Best First'.
Re^4: Multi-threaded behavior, file handle dups and writing to a file by cganote (Initiate) on Jan 08, 2014 at 05:52 UTC
For the first lookup of the file with cat, it takes 50 seconds to go from the mounted filesystem to the local /device with a 9GB file; 25 seconds with a 4.6GB file; 46 seconds with a 6GB file. Subsequent cat calls (haha) on the same file take much less time, probably because the file is already loaded in memory (locally or on the filesystem side, I'm not sure), on the order of 1 - 3 seconds.	[reply]