He talk about reading big files, so I make some test and I found out that I have this problem too, even with noop:
This time (just reading a big file from a sata disk, not using a pendrive) the system become really unusable!
On the home pc, where I never seen problem writing large file using CFQ, I don't have this problem too.
so, may be it's not a scheduler problem, but something else, and changing the scheduler just alleviate the problem...
Is it possible?
How can I find out if it's a latency problem as described in 343371?
Looking around I found this bug:
https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/343371
He talk about reading big files, so I make some test and I found out that I have this problem too, even with noop:
This time (just reading a big file from a sata disk, not using a pendrive) the system become really unusable!
On the home pc, where I never seen problem writing large file using CFQ, I don't have this problem too.
so, may be it's not a scheduler problem, but something else, and changing the scheduler just alleviate the problem...
Is it possible?
How can I find out if it's a latency problem as described in 343371?