Joel Becker <Joel.Becker@oracle.com> wrote:
>
>
> WimMark I report for 2.5.64-mm2
>
> Runs with deadline scheduler: 1580.10 1537.95
> Runs with anticipatory scheduler: 632.87 597.33 555.19
The anticipatory scheduler will never be better than deadline with these
sorts of workloads. The best we can do is to equal it.
With other OLTP-style tests, AS is at worst 5-10% behind deadline.
So what's up with WimMark? Is it possible that the test is exhibiting some
nonlinearity, wherein a small change in inputs causes a large swing in
output?
One way to tell that would be to perform several runs with different values
of /sys/block/sdXX/io_sched/antic_expire. And see how the overall runtime
varies as that is altered.
The default it currently 10 (milliseconds). With zero you should get the
same throughput as deadline.
I'm not sure what to conclude from this result. Can you shed any light on
what it means, on what's going on?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Mar 15 2003 - 22:00:23 EST