Comment 10 for bug 1709889

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2017-08-16 08:17 EDT-------
Even with all three of those patches, I still am seeing delayed I/Os. The pattern looks the same, but I will run for 12+ hours to collect more data. At this point, though, I believe that "cfq" should not be the default scheduler. Are there reasons that it should be the default? What is the background behind the choice to make it the default in Ubuntu? Looking at the upstream code, it seems that if no config parameter is used that the default will be "deadline" (mq-deadline).