Cache tiering
jnickel
12 Posts
November 21, 2019, 11:30 pmQuote from jnickel on November 21, 2019, 11:30 pmHi,
According to this article: https://blog.mellanox.com/2016/02/making-ceph-faster-lessons-from-performance-testing/
"Newer versions of Ceph support cache tiering (first introduced in Firefly, improved in Hammer) which allows the most frequently used data on each node to live on flash while the less frequently used data lives on spinning disk."
This was back in 2016, so I have to assume that this is a feature in PetaSAN - is it?
If I just add SSD OSDs instead of adding them as Journal, then will PetaSAN move the most used data to the SSD as indicated above?
Jim
Hi,
According to this article: https://blog.mellanox.com/2016/02/making-ceph-faster-lessons-from-performance-testing/
"Newer versions of Ceph support cache tiering (first introduced in Firefly, improved in Hammer) which allows the most frequently used data on each node to live on flash while the less frequently used data lives on spinning disk."
This was back in 2016, so I have to assume that this is a feature in PetaSAN - is it?
If I just add SSD OSDs instead of adding them as Journal, then will PetaSAN move the most used data to the SSD as indicated above?
Jim
admin
2,930 Posts
November 21, 2019, 11:48 pmQuote from admin on November 21, 2019, 11:48 pmThis has been deprecated in 2016
Currently you use an SSD as a journal/db device to an HDD, or as an OSD in separate fast / slow pools.
In soon to be released 2.4. we are adding SSD device level cache support.
This has been deprecated in 2016
Currently you use an SSD as a journal/db device to an HDD, or as an OSD in separate fast / slow pools.
In soon to be released 2.4. we are adding SSD device level cache support.
jnickel
12 Posts
November 22, 2019, 12:21 amQuote from jnickel on November 22, 2019, 12:21 amOh cool! Are you able to say how soon that will be released?
Oh cool! Are you able to say how soon that will be released?
Cache tiering
jnickel
12 Posts
Quote from jnickel on November 21, 2019, 11:30 pmHi,
According to this article: https://blog.mellanox.com/2016/02/making-ceph-faster-lessons-from-performance-testing/
"Newer versions of Ceph support cache tiering (first introduced in Firefly, improved in Hammer) which allows the most frequently used data on each node to live on flash while the less frequently used data lives on spinning disk."
This was back in 2016, so I have to assume that this is a feature in PetaSAN - is it?
If I just add SSD OSDs instead of adding them as Journal, then will PetaSAN move the most used data to the SSD as indicated above?
Jim
Hi,
According to this article: https://blog.mellanox.com/2016/02/making-ceph-faster-lessons-from-performance-testing/
"Newer versions of Ceph support cache tiering (first introduced in Firefly, improved in Hammer) which allows the most frequently used data on each node to live on flash while the less frequently used data lives on spinning disk."
This was back in 2016, so I have to assume that this is a feature in PetaSAN - is it?
If I just add SSD OSDs instead of adding them as Journal, then will PetaSAN move the most used data to the SSD as indicated above?
Jim
admin
2,930 Posts
Quote from admin on November 21, 2019, 11:48 pmThis has been deprecated in 2016
Currently you use an SSD as a journal/db device to an HDD, or as an OSD in separate fast / slow pools.
In soon to be released 2.4. we are adding SSD device level cache support.
This has been deprecated in 2016
Currently you use an SSD as a journal/db device to an HDD, or as an OSD in separate fast / slow pools.
In soon to be released 2.4. we are adding SSD device level cache support.
jnickel
12 Posts
Quote from jnickel on November 22, 2019, 12:21 amOh cool! Are you able to say how soon that will be released?
Oh cool! Are you able to say how soon that will be released?