Skip to contentSkip to conversation

speed up dirty data cleaning

DISCUSSION Stefan Priebe - Profihost AG 2 participants 4 messages Nov 7, 2013 – Nov 8, 2013 2 messages not in the archive bcache (block layer cache)

lore
Share & tools
lore
#0 lore raw

Hi,

today i had the problem that my caching device was nearly full and bcache seemed tom react very slowly. Strangely i did not see continues writes to the disk to clean the cache.

Is there any way to speed up dirty data cleaning.

Stefan

A message that is not in the archive (sent off-list or not yet received): 527B90EF.10404-2Lf/[email protected]

#2 lore raw

After some time it seems to start writing out all the data at a good disk speed.

But how does bcache determine when to write which kind of data out of bcache.

Stefan

Am 07.11.2013 14:09, schrieb Stefan Priebe - Profihost AG:

Quoted 10 lines

Hi,

today i had the problem that my caching device was nearly full and bcache seemed tom react very slowly. Strangely i did not see continues writes to the disk to clean the cache.

Is there any way to speed up dirty data cleaning.

Stefan

A message that is not in the archive (sent off-list or not yet received): 527BAF4B.9080609-2Lf/[email protected]

#4 lore raw
Quoted 5 lines · Stefan Priebe - Profihost AG

After some time it seems to start writing out all the data at a good disk speed.

But how does bcache determine when to write which kind of data out of bcache.

There's a PD controller that tries to keep the amount of dirty data at writeback_percent percentage of your cache size. But, since the dirty data account was _still_ broken, that would screw up that PD controller.

Workaround is to set writeback_percent to 0

#5 lore raw

Am 08.11.2013 03:49, schrieb Kent Overstreet:

Quoted 12 lines · Stefan Priebe - Profihost AG
Quoted 5 lines

After some time it seems to start writing out all the data at a good disk speed.

But how does bcache determine when to write which kind of data out of bcache.

There's a PD controller that tries to keep the amount of dirty data at writeback_percent percentage of your cache size. But, since the dirty data account was _still_ broken, that would screw up that PD controller.

Workaround is to set writeback_percent to 0

Tried that but it doesn't seem to start cleaning correctly.

Stefan