Re: [PATCH] migration/calc-dirty-rate: millisecond precision period

2023-08-01 Thread Peter Xu
On Thu, Jun 29, 2023 at 11:59:03AM +0300, Andrei Gudkov wrote: > Introduces alternative argument calc-time-ms, which is the > the same as calc-time but accepts millisecond value. > Millisecond precision allows to make predictions whether > migration will succeed or not. To do this, calculate dirty

Re: [PATCH] migration/calc-dirty-rate: millisecond precision period

2023-08-01 Thread Peter Xu
On Tue, Aug 01, 2023 at 05:55:29PM +0300, gudkov.and...@huawei.com wrote: > Hmmm, such underestimation looks strange to me. I am willing to test > page-sampling and see whether its quality can be improved. Do you have > any specific suggestions on the application to use as a workload? I could have

Re: [PATCH] migration/calc-dirty-rate: millisecond precision period

2023-08-01 Thread gudkov . andrei--- via
On Mon, Jul 31, 2023 at 04:06:24PM -0400, Peter Xu wrote: > Hi, Andrei, > > On Mon, Jul 31, 2023 at 05:51:49PM +0300, gudkov.and...@huawei.com wrote: > > On Mon, Jul 17, 2023 at 03:08:37PM -0400, Peter Xu wrote: > > > On Tue, Jul 11, 2023 at 03:38:18PM +0300, gudkov.and...@huawei.com wrote: > > >

Re: [PATCH] migration/calc-dirty-rate: millisecond precision period

2023-07-31 Thread Peter Xu
Hi, Andrei, On Mon, Jul 31, 2023 at 05:51:49PM +0300, gudkov.and...@huawei.com wrote: > On Mon, Jul 17, 2023 at 03:08:37PM -0400, Peter Xu wrote: > > On Tue, Jul 11, 2023 at 03:38:18PM +0300, gudkov.and...@huawei.com wrote: > > > On Thu, Jul 06, 2023 at 03:23:43PM -0400, Peter Xu wrote: > > > > On

Re: [PATCH] migration/calc-dirty-rate: millisecond precision period

2023-07-31 Thread gudkov . andrei--- via
On Mon, Jul 17, 2023 at 03:08:37PM -0400, Peter Xu wrote: > On Tue, Jul 11, 2023 at 03:38:18PM +0300, gudkov.and...@huawei.com wrote: > > On Thu, Jul 06, 2023 at 03:23:43PM -0400, Peter Xu wrote: > > > On Thu, Jun 29, 2023 at 11:59:03AM +0300, Andrei Gudkov wrote: > > > > Introduces alternative arg

Re: [PATCH] migration/calc-dirty-rate: millisecond precision period

2023-07-17 Thread Peter Xu
On Tue, Jul 11, 2023 at 03:38:18PM +0300, gudkov.and...@huawei.com wrote: > On Thu, Jul 06, 2023 at 03:23:43PM -0400, Peter Xu wrote: > > On Thu, Jun 29, 2023 at 11:59:03AM +0300, Andrei Gudkov wrote: > > > Introduces alternative argument calc-time-ms, which is the > > > the same as calc-time but a

Re: [PATCH] migration/calc-dirty-rate: millisecond precision period

2023-07-11 Thread gudkov . andrei--- via
On Thu, Jul 06, 2023 at 03:23:43PM -0400, Peter Xu wrote: > On Thu, Jun 29, 2023 at 11:59:03AM +0300, Andrei Gudkov wrote: > > Introduces alternative argument calc-time-ms, which is the > > the same as calc-time but accepts millisecond value. > > Millisecond precision allows to make predictions whe

Re: [PATCH] migration/calc-dirty-rate: millisecond precision period

2023-07-06 Thread Peter Xu
On Thu, Jun 29, 2023 at 11:59:03AM +0300, Andrei Gudkov wrote: > Introduces alternative argument calc-time-ms, which is the > the same as calc-time but accepts millisecond value. > Millisecond precision allows to make predictions whether > migration will succeed or not. To do this, calculate dirty

[PATCH] migration/calc-dirty-rate: millisecond precision period

2023-06-29 Thread Andrei Gudkov via
Introduces alternative argument calc-time-ms, which is the the same as calc-time but accepts millisecond value. Millisecond precision allows to make predictions whether migration will succeed or not. To do this, calculate dirty rate with calc-time-ms set to max allowed downtime, convert measured ra