Sridhar,
Thanks a lot for this explantation. It's clearer now.
So at the end of the day (at least with balanced profile) it's a lower bound
and no upper limit and a balanced distribution between client and cluster IOPS.
Regards,
Frédéric.
-Message original-
De:
Hello Frédéric,
Please see answers below.
> Could someone please explain how mclock works regarding reads and writes?
> Does mclock intervene on both read and write iops? Or only on reads or only
> on writes?
>
mClock schedules both read and write ops.
>
> And what type of underlying
There was a client SSD sorta like that, a bit of Optane with TLC or QLC, but it
didn't seem to sell well. Optane was groovy tech, but with certain challenges
as well.
> On Jan 9, 2024, at 14:30, Mark Nelson wrote:
>
> With HDDs and a lot of metadata, it's tough to get away from it imho. In
With HDDs and a lot of metadata, it's tough to get away from it imho.
In an alternate universe it would have been really neat if Intel could
have worked with the HDD vendors to put like 16GB of user accessible
optane on every HDD. Enough for the WAL and L0 (and maybe L1).
Mark
On 1/9/24
Not strictly an answer to your worthy question, but IMHO this supports my
stance that hybrid OSDs aren't worth the hassle.
> On Jan 9, 2024, at 06:13, Frédéric Nass
> wrote:
>
> With hybrid setups (RocksDB+WAL on SSDs or NVMes and Data on HDD), if mclock
> only considers write performance,
