Re: [PATCH][CFT] new IO scheduler for 2.4.20

Neil Schemenauer (nas@python.ca)
Sun, 20 Apr 2003 18:46:04 -0700


Marc-Christian Petersen wrote:
> what about i/o throughput, bonnie or such?

bonnie++
Version 1.03 ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
2.4.20 1G 36236 18 13423 7 29948 11 210.1 0
2.4.20-nas1 1G 35998 18 12076 7 19056 9 206.7 0
2.4.20-nas2 1G 37450 18 12101 7 19363 9 210.7 0

Read throughput has definitely taken a hit. I don't know why. Perhaps
the elevator needs to have a little more relaxed definition of
contiguous requests. Right now it only puts requests together if they
are perfectly contiguous (the first sector in one request is the next
after the last sector of another). I'll try to test that.

Any other theories?

Neil
-
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/