Each fragment is part of a specific object. No two objects share a fragment. I don't think making the fragments contiguous will be of much benefit. Either the system is not busy, in which case the additional seek time doesn't matter, or it's busy in which case many other objects are being read and written simultaneously on the disk and therefore you won't get large contiguous reads in any case. Objects are read as they can be written to the network, not all at once. Once a socket buffer is full its better to read a fragment for another object to fill a different socket buffer.
On Wednesday, May 31, 2017, 8:52:08 PM CDT, Anh Le Duc (2) <anh...@vng.com.vn> wrote: Thanks Alan. Does a fragment store only one object? I understand: > The difficulty in making fragments for a single object contiguous is the data arrives non-contiguously. Our objects are split and stored into may-be-not-contiguous fragments. Do you think it's a good idea to tweak the GC to re-order fragments?
