Another path that we have been investigating is to use some NVMe on the
database machine as a cache (bcache, cachefs, etc). Several TB of U.2
drives in a striped-LVM should enhance performance for 'hot' data and
cover for the issues of storing a large DB in Ceph.
Note that we haven't tried this yet, but there are at least some
discussions for MySQL.
-Dave
Dave Hall
Binghamton University
On 10/19/2020 10:49 PM, Brian Topping wrote:
Another option is to let PosgreSQL do the replication with local storage. There
are great reasons for Ceph, but databases optimize for this kind of thing
extremely well.
With replication in hand, run snapshots to RADOS buckets for long term storage.
On Oct 17, 2020, at 7:28 AM, Gencer W. Genç <gen...@gencgiyen.com> wrote:
Hi,
I have an existing few RBDs. I would like to create a new RBD Image for
PostgreSQL. Do you have any suggestions for such use cases? For example;
Currently defaults are:
Object size (4MB) and Stripe Unit (None)
Features: Deep flatten + Layering + Exclusive Lock + Object Map + FastDiff
Should I use as is or should I use 16KB of object size and different sets of
features for PostgreSQL?
Thanks,
Gencer.
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
