Re: [SRU] Set the default IO scheduler to CFQ in Kubuntu Trusty
On Thu, Oct 9, 2014 at 6:32 PM, Stephen Michael Kellat wrote: > On Thu, 9 Oct 2014 18:15:17 +0200 > Rohan Garg wrote: > > [snip] >> > >> > I thought that Edubuntu was still including both Ubuntu and Kubuntu >> > on their DVD, which would be a clear example of why this would be >> > the case. It doesn't look like Kubuntu is on that image anymore, >> > so maybe this is a negligible use case. >> > >> >> The udev rule is shipped via the kubuntu-settings package which does >> not land in the Edubuntu install manifest [1]. So I'm pretty sure >> this does not impact them at all. >> >> Cheers >> Rohan Garg >> >> [1] >> http://cdimages.ubuntu.com/xubuntu/releases/trusty/release/xubuntu-14.04-desktop-amd64.manifest > [snip] > > That would actually be our manifest out in Xubuntu country, I would suggest > consulting this instead for Edubuntu's manifest: > > http://cdimages.ubuntu.com/edubuntu/releases/14.04.1/release/edubuntu-14.04-dvd-amd64.manifest > Whoops, thanks for that :) Manifest still has no kubuntu-settings-* packages though. Cheers Rohan Garg -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Re: [SRU] Set the default IO scheduler to CFQ in Kubuntu Trusty
Hi > As I said, the switch to deadline was seen to address existing problems with > applications on the unity desktop (when running on an HDD) becoming > non-responsive under heavy I/O. Switching back to cfq is likely to > reintroduce this problem. > Right and this data is fairly out of date right? I mean, is there up to date data on whether or not switching to CFQ will definitely cause issues in Unity? I'd rather work with data which we have right now ( general feedback from users suggests that baloo performance is quite bad with deadline and improves with the switch to CFQ ) rather than making assumptions based on outdated data. >> but the pro's of changing the scheduler to cfq in order to get better >> performance in a KDE session >> outweigh this performance hit ( if there is one ). > > How do they outweigh it? I think you can only say they outweigh it if > you're running the Kubuntu desktop. If you're running the Ubuntu desktop, > but have the Kubuntu desktop installed, you will have a different > assessment. > > I thought that Edubuntu was still including both Ubuntu and Kubuntu on their > DVD, which would be a clear example of why this would be the case. It > doesn't look like Kubuntu is on that image anymore, so maybe this is a > negligible use case. > The udev rule is shipped via the kubuntu-settings package which does not land in the Edubuntu install manifest [1]. So I'm pretty sure this does not impact them at all. Cheers Rohan Garg [1] http://cdimages.ubuntu.com/xubuntu/releases/trusty/release/xubuntu-14.04-desktop-amd64.manifest -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Re: [SRU] Set the default IO scheduler to CFQ in Kubuntu Trusty
On Thu, Oct 09, 2014 at 05:39:33PM +0200, Rohan Garg wrote: > > So while I still don't agree that this is free of risk of regression (e.g., > > a system with both kubuntu and ubuntu desktops installed could see a direct > > regression under the ubuntu session as a result of this change), I also > > Could you elaborate a bit on how this would affect the unity session? Sure > performance might take a hit in certain cases, and we're very well > aware of that, As I said, the switch to deadline was seen to address existing problems with applications on the unity desktop (when running on an HDD) becoming non-responsive under heavy I/O. Switching back to cfq is likely to reintroduce this problem. > but the pro's of changing the scheduler to cfq in order to get better > performance in a KDE session > outweigh this performance hit ( if there is one ). How do they outweigh it? I think you can only say they outweigh it if you're running the Kubuntu desktop. If you're running the Ubuntu desktop, but have the Kubuntu desktop installed, you will have a different assessment. I thought that Edubuntu was still including both Ubuntu and Kubuntu on their DVD, which would be a clear example of why this would be the case. It doesn't look like Kubuntu is on that image anymore, so maybe this is a negligible use case. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Re: [SRU] Set the default IO scheduler to CFQ in Kubuntu Trusty
> So while I still don't agree that this is free of risk of regression (e.g., > a system with both kubuntu and ubuntu desktops installed could see a direct > regression under the ubuntu session as a result of this change), I also Could you elaborate a bit on how this would affect the unity session? Sure performance might take a hit in certain cases, and we're very well aware of that, but the pro's of changing the scheduler to cfq in order to get better performance in a KDE session outweigh this performance hit ( if there is one ). And could be we move forward with the SRU itself? Anyone want to approve it from the -proposed queue? Cheers Rohan Garg -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Muon + APT CI
Hi, We've talked about this many times but we never took action. Muon has APT tests (few, but some). It would be great to have them running somewhere. Do you guys think Kubuntu could do this? Aleix -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Re: [SRU] Set the default IO scheduler to CFQ in Kubuntu Trusty
On Thu, Oct 9, 2014 at 8:07 AM, Martin Pitt wrote: > Steve Langasek [2014-10-08 13:10 -0700]: >> It has been pointed out that Ubuntu also has an indexer, zeitgeist, which >> apparently doesn't suffer from the same problem. > > To clarify: For the most part, zeitgeist only stores access events, i. > e. metadata like "accessed this video at this time". There have been > some experiments with making it index full file contents, but I don't > believe we have/use that. > > In earlier Ubuntu releases we used to install various file content > indexers by default (like tracker), and in the end they all sucked. By > nature they are using ginormous I/O and nontrivial CPU bandwidth all > the time, causing both desktop slowdown and much higher battery drain. > > So the desktop team decided some time ago to not install a file > indexer by default. People who actually do want this can install > tracker. The desktop slowdown can probably be addressed with some > clever scheduler/ionice/whatever magic, but the cpu/IO/power usage > will not go down no matter how you schedule things. > > Martin > > -- > Martin Pitt| http://www.piware.de > Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) > > -- > Ubuntu-release mailing list > ubuntu-rele...@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-release > Just as a side note, the udev rule that I introduced only changes the scheduler for rotational media. If the disk is a SSD, there is no change to the scheduler. Cheers Rohan Garg -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
