From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juri Lelli Subject: Re: [PATCH 2/2] sched/fair: util_est: add running_sum tracking Date: Tue, 5 Jun 2018 17:31:05 +0200 Message-ID: <20180605153105.GM16081@localhost.localdomain> References: <20180604160600.22052-1-patrick.bellasi@arm.com> <20180604160600.22052-3-patrick.bellasi@arm.com> <20180605151129.GC32302@e110439-lin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20180605151129.GC32302@e110439-lin> Sender: linux-kernel-owner@vger.kernel.org To: Patrick Bellasi Cc: Vincent Guittot , linux-kernel , "open list:THERMAL" , Ingo Molnar , Peter Zijlstra , "Rafael J . Wysocki" , Viresh Kumar , Dietmar Eggemann , Morten Rasmussen , Joel Fernandes , Steve Muckle , Todd Kjos List-Id: linux-pm@vger.kernel.org On 05/06/18 16:11, Patrick Bellasi wrote: [...] > If I run an experiment with your example above, while using the > performance governor to rule out any possible scale invariance > difference, here is what I measure: > > Task1 (40ms delayed by the following Task2): > mean std max > running_avg 455.387449 22.940168 492.0 > util_avg 433.233288 17.395477 458.0 > > Task2 (waking up at same time of Task1 and running before): > mean std max > running_avg 430.281834 22.405175 455.0 > util_avg 421.745331 22.098873 456.0 > > and if I compare Task1 above with another experiment where Task1 is > running alone: > > Task1 (running alone): > mean std min > running_avg 460.257895 22.103704 460.0 > util_avg 435.119737 17.647556 461.0 Wait, why again in this last case running_avg != util_avg? :)