You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In moss, it might have a large segment (many megabytes) that needs to be written or appended to the end of the file.
Is it more efficient to call pwrite() once with the entire segment's large data buffer, where perhaps the OS/filesystem knows how to efficiently split that up into concurrent I/O channel use...
...or, should moss split the big buffer into multiple, smaller, block-aligned sections, where moss can spawn off multiple goroutines to invoke several pwrite()'s concurrently.
Which one is faster / utilizes more I/O bandwidth or channels?
The text was updated successfully, but these errors were encountered:
steveyen
changed the title
is a large pwrite() faster than many concurrent smaller pwrite()'s?
is a large pwrite() more efficient than many concurrent smaller pwrite()'s?
May 9, 2017
In moss, it might have a large segment (many megabytes) that needs to be written or appended to the end of the file.
Is it more efficient to call pwrite() once with the entire segment's large data buffer, where perhaps the OS/filesystem knows how to efficiently split that up into concurrent I/O channel use...
...or, should moss split the big buffer into multiple, smaller, block-aligned sections, where moss can spawn off multiple goroutines to invoke several pwrite()'s concurrently.
Which one is faster / utilizes more I/O bandwidth or channels?
The text was updated successfully, but these errors were encountered: