search

junneyang / zumastor

Automatically exported from code.google.com/p/zumastor
0 stars 1 forks source link

'ddsnap status' can become really slow after a large volume get aged #130

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
'ddsnap status' can take extremely long time (i.e., some minutes) to
complete when the size of the zumastor volume is large (like some hundreds
of GB) and the volume is aged after several snapshot creations and
deletions. The problem is a side-effect of issue 5. But Chris's AIO patch
may help even though the btree does not fit in memory. Currently, setting
'--cachesize' of 'zumastor define volume' to a larger value may help to
lighten the problem.

Original issue reported on code.google.com by jiahotc...@gmail.com on 8 May 2008 at 7:02

GoogleCodeExporter commented 9 years ago

Original comment by daniel.r...@gmail.com on 14 May 2008 at 6:50

GoogleCodeExporter commented 9 years ago 
Committed revision 1671 adds metadata usuage in 'ddsnap status'. Users can 
increase
ddsnap buffer size with the --cachesize option of the 'ddsnap server' command. 
This
will speed up 'ddsnap status' after the first call if the metadata can fit in 
memory.

A new issue 149: Use AIO to read metadata in 'ddsnap status'
is entered for speeding up 'ddsnap staus' when the metadata does not fit in 
memory.

Original comment by jiahotc...@gmail.com on 28 May 2008 at 7:07