Hello everybody, A simple experiment: start my ext3 Jaunty install yet forcing the use of only one processor core, by having added maxcpus=1 in the kernel parameters list inside /boot/grub/menu.lst
The result is just as bad as usual. Not as bad as when forcing the tar command and Firefox to use the same core when the two cores are available... but just very annoying as usual. So, while the problem obviously can be made better or worse by fiddling with the interactions between cores, and this will help a lot of people in the meanwhile, it does not seem to be fundamentally SMP-related. I tried maxcpus=1 on the ext4 install... but there was no feelable penalty. Firefox started and quit and behaved very fluently despite the tar command proceeding. Actually, this is an enjoying way of life I was sad to loose on Linux maybe 5 years ago. For a while I could better the situation by tuning the kernel parameters and changing some of its source code. Then it became completely unhackable and I got used to stop everything else before starting a video game or playing a DVD. When I acquired a two-cores machine, two years ago, I thought it would help but it merely didn't. I'm very happy the situation is back to an efficient near-real-time operating system. I'm puzzled by what may have been lost in ext3 to lead to this... or what has been innovated in ext4... Maybe the enhancements in the kernel scheduling algorithms made them incompatible with the habits of ext3... -- [jaunty] cpu scheduling is not optimized for multitask https://bugs.launchpad.net/bugs/363663 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
