Re: SSD journal partition and trim

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Most likely. When fully provisioned the device has a much smaller pool of cells to manage (i.e. charge) in the background, hence once that pool is exhausted the device has no option but to stall whilst it clears (re-charges) a cell, which takes something like 2-5ms.

Daily cron task is though still a good idea - enabling discard mount option is generally counter-productive since trim is issue way too often, destroying performance (in my testing).

On 2013-12-03 13:12, Emmanuel Lacour wrote:
On Tue, Dec 03, 2013 at 12:48:21PM +0000, James Pearce wrote:
How much (%) is left unprovisioned on those (840s?) ?  And were they
trim'd/secure erased before deployment?


unfortunatly, everything was provisioned (thought, there is free spaces
in the VG) due to lack of knowledge.

Nothing special was made before running the cluster, just a somewhat
standard Debian install on top of those SSDs.

That may explain we needed to run fstrim (I added a daily cron for
this).


_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux