Maybe it is easier to tell in this way.
What we want to see is that the newly written data to stay in the
journal disk for as long as possible such that write workloads do not
compete for disk headers for read workloads. Any way to achieve that in
Ceph? Thanks,
Xing
On 03/04/2013 09:55 AM, Gregory Farnum wrote:
The "journal [min|max] sync interval" values specify how frequently
the OSD's "FileStore" sends a sync to the disk. However, data is still
written into the normal filesystem as it comes in, and the normal
filesystem continues to schedule normal dirty data writeouts. This is
good — it means that when we do send a sync down you don't need to
wait for all (30 seconds * 100MB/s) 3GB or whatever of data to go to
disk before it's completed.
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
