Dne 24. 03. 20 v 23:35 Gionatan Danti napsal(a):
Il 2020-03-24 16:09 Zdenek Kabelac ha scritto:
In past we had problem that when users have been using huge chunk size,
and small 'migration_threashold' - the cache was unable to demote chunks
from the cache to the origin device (the size of 'required' data for
demotion were bigger then what has been allowed by threshold).
So lvm2/libdm implemented protection to always set at least 8 chunks
is the bare minimum.
Now we face clearly the problem from 'the other side' - users have way
too big chunks (we've seen users with 128M chunks) - and so threshold
is set to 1G
and users are facing serious bottleneck on the cache side doing to many
promotions/demotions.
We will likely fix this by setting max chunk size somewhere around 2MiB. >
Thanks for the explanation. Maybe is a naive proposal, but can't you simply
set migration_threshold equal to a single chunk for >2M sized chunks, and 8
chunks for smaller ones?
Using large cache chunks likely degrades the usefulness and purpose of cache.
Though we are missing some comparative tables showing how the
optimal layouts should look like.
So the idea is not to just 'let it somehow work' but rather to move it towards
more efficient usage of available resources.
Zdenek
_______________________________________________
linux-lvm mailing list
linux-lvm@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
