On Thu, 13 Dec 2018 13:42:24 +0100 Paolo Valente <paolo.valente@xxxxxxxxxx> wrote: > To test the behavior of your system, why don't you check, e.g., how > long it takes to start an application while there is some background > I/O? > > A super quick way to do this is > > git clone https://github.com/Algodev-github/S > cd S/comm_startup_lat > sudo ./comm_startup_lat.sh <scheduler-you-want-to-test> 5 5 seq 3 > "replay-startup-io gnometerm" > > The last command line > - starts the reading of 5 files plus the writing of 5 other files > - replays, for three times, the I/O that gnome terminal does while; > starting up (if you want I can tell you how to change the last > command line so as to execute the original application, but you would > get the same results); > - for each attempt, measures how long this start-up I/O takes to > complete. Thanks for this. I suspect I wasn't really stressing my system when I was evaluating it, and it was subjective. I'm running a kernel with cfq right now, but I will boot the noop kernel when I get a chance and test it. I suppose I could just switch to noop io scheduling instead. Should be interesting. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
