Messages in this thread | | | Subject | RE: [PATCH] sched: Folding nohz load accounting more accurate | From | Peter Zijlstra <> | Date | Wed, 13 Jun 2012 23:57:33 +0200 |
| |
On Wed, 2012-06-13 at 08:33 -0700, Doug Smythies wrote: > > All that being said, what I typically do with a new code test is: > > . select a known, previous bad operating point. For example 2 > processes, actual load average 0.30 (0.15 for each process) currently > reporting ~1.5.
OK, I'll try and apply this. Waiting 63 hours for feedback on patches is something I'm not patient enough for.
Would this be:
./waiter 2 900 230608 10000
I haven't even bothered reading the waiter proglet yet, but I did notice the 'help' provided when started without arguments doesn't seem to actually match what load_180 does.
| |