summaryrefslogtreecommitdiffstats
path: root/xlators/performance/md-cache
diff options
context:
space:
mode:
authorPoornima G <pgurusid@redhat.com>2018-02-09 10:33:30 +0530
committerRaghavendra G <rgowdapp@redhat.com>2018-02-26 17:28:26 +0000
commit4a8255f772c8e98ccf6cae731d4d665363c3ed81 (patch)
tree83c162ddbc374b36871de9fc01c2ea6afeb35b89 /xlators/performance/md-cache
parent7d641313f46789ec0a7ba0cc04f504724c780855 (diff)
write-behind: Make aggregate size configurable
Currently the aggregate size is by default 128K (page size). From performance perspective small number of large writes is faster than large number of small writes, especially in EC volumes. But identifying the right aggregate size depends on multiple factors like the memcpy overhead, network overhead etc. On local machine, combining 128k writes to 1M writes for EC volumes yielded 30% improvement. As a part of this patch, aggregate size is just made configurable and page_size is modified accordingly. Raghavendra Gowdappa had suggested that, while aggregating writes we should get rid of memcpy of large write size, and instead add the pointer to existinf vector, will be doing it as a part of another patch. Also, in EC volumes, the vectors are merged into one vector, so even if we save memcopy in write_behind, EC would anyways do memcopy for merging vectors into one vector. Updates: #364 Change-Id: Ib67294b8577bea14dde1c84cd271012ecea99f09 Signed-off-by: Poornima G <pgurusid@redhat.com>
Diffstat (limited to 'xlators/performance/md-cache')
0 files changed, 0 insertions, 0 deletions