WOW, this fix worked for me still in Ubuntu 13.10 I have in my laptop
combined SSD, HDD, External HDD and USB Sticks (from time to time) and
copying files got my system stuck always, but after changing to deadline
it seems to be fixed
--
You received this bug notification because you are a
i think that the default I/O scheduler
should be change from CFQ to deadline
deadline I/O scheduler is good with both
SSD (solid-state-drives) and HDD (Hard disk drive)
--
source:
Chauncellor,
Please don't reopen closed bugs. If you are affected by an issue, please
file a new bug.
Thanks!
~JFo
** Changed in: linux (Ubuntu)
Status: Confirmed = Invalid
--
CFQ may not be the right choice of i/o scheduler for the most common desktop
systems
This bug report was marked as Incomplete and has not had any updated
comments for quite some time. As a result this bug is being closed.
Please reopen if this is still an issue in the current Ubuntu release
http://www.ubuntu.com/getubuntu/download . Also, please be sure to
provide any requested
** Changed in: linux (Ubuntu)
Status: Expired = Confirmed
--
CFQ may not be the right choice of i/o scheduler for the most common desktop
systems
https://bugs.launchpad.net/bugs/427210
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I installed a fresh copy of Lucid after upgrading since Jaunty. It took
me a while to remember why my computer was being so INCREDIBLY sluggish.
I was actually starting to get angry.
Bless you, deadline. Linux is so much more enjoyable with you in my
pocket.
--
CFQ may not be the right choice
This bug report was marked as Triaged a while ago but has not had any
updated comments for quite some time. Please let us know if this issue
remains in the current Ubuntu release,
http://www.ubuntu.com/getubuntu/download . If the issue remains, click
on the current status under the Status column
Hi guys,
For those of you following along here, you'll likely want to also pay
attention to bug 381300.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/381300/comments/17
It seems the CFQ scheduler has some issues even with SSDs, so I'm gonna
experiment with changing the default to
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Status: New = Triaged
--
CFQ may not be the right choice of i/o scheduler for the most common desktop
systems
https://bugs.launchpad.net/bugs/427210
You received this bug notification because
For ssds the best scheduler to use is noop, there is no point shuffling
around data to optimise for mechanical hard disks when accessing what is
essentially a random access disk.
That is another gripe I have with the disk schedulers in ubuntu, for
flash drives the scheduler should ALWAYS be noop.
One thing I've noticed since I've changed to deadline is that when I get
to the GDM login screen, it's significantly less responsive. Today, it
actually took about 15 seconds before I could type in my login and
password.
I did do lots of hardware changes, though. Might it have been the
computer
In my case the difference was obvious with a consumer HD (WD AAKS).
Note that the new kernel in 9.10 seems also to be a good improvement.
best,
Paulo
2009/9/11 trumpeteersman trumpeteers...@gmail.com:
What kind of storage devices are you guys using? Performance HDDS?
Consumer HHDs? SSDs?
I am using cheap consumer HDDs (WD 1.5TB 5400rpm)
--
CFQ may not be the right choice of i/o scheduler for the most common desktop
systems
https://bugs.launchpad.net/bugs/427210
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Generic Seagate 200 GB at 7400 RPM.
Nothing special.
--
CFQ may not be the right choice of i/o scheduler for the most common desktop
systems
https://bugs.launchpad.net/bugs/427210
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I switched to deadline on the fly during a file transfer to USB and
noticed an immediate difference in the system responsiveness, though the
operations didn't seem to change their data rate, the screen started
updating and the system was much more usable. Definitely closer to what
I'd expect from
I can confirm the massive increase using the deadline schedule. I'm
writing it right now while I'm executing the dd command, and it's only
hiccuped once, and not by much at all. It's almost like it's back to
where it used to be on responsiveness. 95 percent there.
--
CFQ may not be the right
Wow, that's made a difference when using deadline
Many thanks.
--
CFQ may not be the right choice of i/o scheduler for the most common desktop
systems
https://bugs.launchpad.net/bugs/427210
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Wow, that's made a difference when using deadline
Many thanks.
--
CFQ may not be the right choice of i/o scheduler for the most common desktop
systems
https://bugs.launchpad.net/bugs/427210
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
What kind of storage devices are you guys using? Performance HDDS?
Consumer HHDs? SSDs?
--
CFQ may not be the right choice of i/o scheduler for the most common desktop
systems
https://bugs.launchpad.net/bugs/427210
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/31580108/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/31580110/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/31580112/Dependencies.txt
**
I've been running with the anticipatory scheduler for a long time now.
The same bug drove me to experiment with the schedulers. Responsiveness
under heavy I/O is much better than with CFQ
Every once in a while (when changing kernels) I try CFQ again, without
luck. I know CFQ has a few kernel
** Description changed:
Ubuntu currently uses the kernel default i/o scheduler, CFQ. I strongly
believe that this is the wrong scheduler to use for the vast majority of
likely Ubuntu desktop installs because it causes huge lag in interactive
applications under the heavy kind of i/o
22 matches
Mail list logo
