© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I don't think, that it is not a scheduler problem only. Switching the scheduler does not result in significant changes. The desktop responsiveness is still bad with all schedulers. The server kernel is less affected, but the desktop responsiveness is still bad.
Fedora and ArchLinux are less affected, but the problem still exists. It's perhaps like using the server kernel in Ubuntu.
For me the problem first appears in Gutsy. Feisty has a great desktop responsiveness on heavy io on my old machine with the cfq scheduler. CentOS with the 2.6.18 kernel and the cfq scheduler works really great.
Once I have produced the same issue with a crash of network manager while transferring a big file through a wlan connection. I think there was not logging io, but I am not sure.
Are there only a few people affected by the problem? It makes my system nearby unusable, while e.g. updating Intrepid. There are sometimes desktop freezes for more than 20 seconds on my machine.