From: dongdong tao
Current way to calculate the writeback rate only considered the
dirty sectors, this usually works fine when the fragmentation
is not high, but it will give us unreasonable small rate when
we are under a situation that very few dirty sectors consumed
a lot dirty buckets. In
From: dongdong tao
Current way to calculate the writeback rate only considered the
dirty sectors, this usually works fine when the fragmentation
is not high, but it will give us unreasonable small rate when
we are under a situation that very few dirty sectors consumed
a lot dirty buckets. In
Hi Coly,
Apologies for any confusion that I might have caused, and thanks a lot
for your patience and your help !
On Thu, Jan 14, 2021 at 9:31 PM Coly Li wrote:
>
> On 1/14/21 8:22 PM, Dongdong Tao wrote:
> > Hi Coly,
> >
> > Why you limit the iodeph to 8 and iop
erformance number before and
after applying the patch.
Thanks,
Dongdong
On Thu, Jan 14, 2021 at 6:05 PM Coly Li wrote:
>
> On 1/14/21 12:45 PM, Dongdong Tao wrote:
> > Hi Coly,
> >
> > I've got the testing data for multiple threads with larger IO depth.
> >
>
[Share the google doc here to avoid SPAM detection]
Here is the new testing result with multiple threads fio testing:
https://docs.google.com/document/d/1AmbIEa_2MhB9bqhC3rfga9tp7n9YX9PLn0jSUxscVW0/edit?usp=sharing
On Fri, Jan 8, 2021 at 4:47 PM Dongdong Tao wrote:
>
> Yeap, I will sca
Yeap, I will scale the testing for multiple threads with larger IO
depth, thanks for the suggestion!
On Fri, Jan 8, 2021 at 4:40 PM Coly Li wrote:
>
> On 1/8/21 4:30 PM, Dongdong Tao wrote:
> > Hi Coly,
> >
> > They are captured with the same time length, the meaning of t
_percent dropped to around 30.
Regards,
Dongdong
On Fri, Jan 8, 2021 at 12:06 PM Coly Li wrote:
>
> On 1/7/21 10:55 PM, Dongdong Tao wrote:
> > Hi Coly,
> >
> >
> > Thanks for the reminder, I understand that the rate is only a hint of
> > the throughput, it’s
From: dongdong tao
Current way to calculate the writeback rate only considered the
dirty sectors, this usually works fine when the fragmentation
is not high, but it will give us unreasonable small rate when
we are under a situation that very few dirty sectors consumed
a lot dirty buckets. In
percent is above that
Thanks,
Dongdong
On Wed, Dec 9, 2020 at 10:27 AM Dongsheng Yang
wrote:
>
>
> 在 2020/11/3 星期二 下午 8:42, Dongdong Tao 写道:
> > From: dongdong tao
> >
> > Current way to calculate the writeback rate only considered the
> > dirty sectors, thi
producer is
just an easy way to reproduce it.
Regards,
Dongdong
On Fri, Nov 6, 2020 at 12:32 AM Coly Li wrote:
>
> On 2020/11/3 20:42, Dongdong Tao wrote:
> > From: dongdong tao
> >
> > Current way to calculate the writeback rate only considered the
> > dirty sect
From: dongdong tao
commit 9aaf51654672 ("bcache: make cutoff_writeback and
cutoff_writeback_sync tunable") intend to make these two option
configurable by user, but these two are still read-only.
Signed-off-by: dongdong tao
---
drivers/md/bcache/sysfs.c | 6 --
1 file
From: dongdong tao
Current way to calculate the writeback rate only considered the
dirty sectors, this usually works fine when the fragmentation
is not high, but it will give us unreasonable small rate when
we are under a situation that very few dirty sectors consumed
a lot dirty buckets. In
12 matches
Mail list logo
