I was wondering if there is anywhere I can find thorough documentation on memstore and if there are any documented use cases? As the only documentation, I can find is https://ceph.io/geen-categorie/ceph-real-men-use-the-memstore-backend/ Thanks Gabryel Mason-Williams, Placement Student Address: Diamond Light Source Ltd., Diamond House, Harwell Science & Innovation Campus, Didcot, Oxfordshire OX11 0DE Email: gabryel.mason-williams@diamond.ac.uk -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
On Thu, Sep 26, 2019 at 11:50 PM Mason-Williams, Gabryel (DLSLtd,RAL,LSCI) <gabryel.mason-williams@diamond.ac.uk> wrote:
I was wondering if there is anywhere I can find thorough documentation on memstore and if there are any documented use cases? As the only documentation, I can find is https://ceph.io/geen-categorie/ceph-real-men-use-the-memstore-backend/
hi Gabryel, as memstore is a very simple object store backend. i am afraid we don't have a thorough document on it at this moment. probably the best reference is its source code. i think the use cases of memstore is for profiling and prototyping, as its name suggests, memstore is an in-memory store. so one can expect that all I/O targeting it will finish in a jiffy. this property helps us to identify the bottleneck in the other parts of OSD, for instance, the messenger, OSD and PG. currently, we are developing a next generation OSD dubbed "crimson", which is also using a variant of memstore for testing. -- Regards Kefu Chai
participants (2)
-
kefu chai
-
Mason-Williams, Gabryel (DLSLtd,RAL,LSCI)