Could you run that test again with /usr/bin/time (the GNU time
function) so we can see what kind of swapping it's doing?
The use-once approach depends on having a fairly stable inactive_dirty
+ inactive_clean queue size, to give use-often pages a fair chance to
be rescued. To see how the sizes of the queues are changing, use
Shift-ScrollLock on your text console.
To tell the truth, I don't have a deep understanding of how dbench
works. I should read the code now and see if I can learn more about it
:-/ I have noticed that it tends to be highly variable in performance,
sometimes showing variation of a few 10's of percents from run to run.
This variation seems to depend a lot on scheduling. Do you see "*"'s
evenly spaced throughout the tracing output, or do you see most of them
bunched up near the end?
-- Daniel - 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/