Re: smem report from the nexus-raring
On 04/25/2013 08:00 PM, Sebastien Bacher wrote: Le 25/04/2013 18:06, Sebastien Bacher a écrit : I will follow up on the list when I have more informations Laney found an issue with glib-networking (relying on DESKTOP_SESSION=gnome for detecting the method to use, where we set it to ubuntu which shouldn't use the fallback mode either) and is working on a fix, details on https://bugs.launchpad.net/glib-networking/+bug/1172792 That will fix the ubuntu-geoip case (which does access proxy through glib), but the problem with libproxy is still there and affects signond/signon-ui which are using libproxy directly, we will need to deal with those as well I suggest looking into a fix in libproxy itself, because it's probably going to be used by all Qt apps starting from Qt 5.1: https://codereview.qt-project.org/46272 Ciao, Alberto -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: smem report from the nexus-raring
Le 28/01/2013 21:06, Sebastien Bacher a écrit : We recently did a smem memory snapshot from raring, running on a nexus tablet. The results have been recorded on the wiki: https://wiki.ubuntu.com/Nexus7/Smem-2013-01-16 Hey everyone, Just as a small status update, since we are wrapping the raring cycle I though it would be good to have an updated snapshot, so I did one yesterday (using the current raring iso): https://wiki.ubuntu.com/Nexus7/Smem-2013-04-24 I wrote down some of the most notable differences in the notes column and added the new/dropped from the list of running processes at the bottom of the page. There is a quite some fluctuation between runs, so it's not easy to say if the small diffs are actual changes or just noise... Cheers, Sebastien Bacher -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: smem report from the nexus-raring
On Thu, Apr 25, 2013 at 10:28:57AM +0200, Sebastien Bacher wrote: Le 28/01/2013 21:06, Sebastien Bacher a écrit : We recently did a smem memory snapshot from raring, running on a nexus tablet. The results have been recorded on the wiki: https://wiki.ubuntu.com/Nexus7/Smem-2013-01-16 Just as a small status update, since we are wrapping the raring cycle I though it would be good to have an updated snapshot, so I did one yesterday (using the current raring iso): https://wiki.ubuntu.com/Nexus7/Smem-2013-04-24 I wrote down some of the most notable differences in the notes column and added the new/dropped from the list of running processes at the bottom of the page. There is a quite some fluctuation between runs, so it's not easy to say if the small diffs are actual changes or just noise... Thanks for this update, Seb! You noted in the list of 'new' processes: pxgsettings processes (libproxy use in geoclue and lenses?) I've noticed this here as well; on my system this comes to 10 processes (5 shells, 5 pxgsettings instances). That looks very wrong to me. Why is this not running as a single dbus service with multiple clients? Is this a priority for the desktop team to look at? -- 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 -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: smem report from the nexus-raring
Le 25/04/2013 17:57, Steve Langasek a écrit : Why is this not running as a single dbus service with multiple clients? Is this a priority for the desktop team to look at? Hey Steve, Good questions, I don't have the answers yet but that's high on my todolist, I will follow up on the list when I have more informations Cheers, Sebastien Bacher -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: smem report from the nexus-raring
On Thu, Apr 25, 2013 at 10:28:57AM +0200, Sebastien Bacher wrote: Le 28/01/2013 21:06, Sebastien Bacher a écrit : We recently did a smem memory snapshot from raring, running on a nexus tablet. The results have been recorded on the wiki: https://wiki.ubuntu.com/Nexus7/Smem-2013-01-16 Hey everyone, Just as a small status update, since we are wrapping the raring cycle I though it would be good to have an updated snapshot, so I did one yesterday (using the current raring iso): https://wiki.ubuntu.com/Nexus7/Smem-2013-04-24 I wrote down some of the most notable differences in the notes column and added the new/dropped from the list of running processes at the bottom of the page. There is a quite some fluctuation between runs, so it's not easy to say if the small diffs are actual changes or just noise... We are displaying some of this data based on testing in the QA lab here: http://reports.qa.ubuntu.com/memory/ Joe -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: smem report from the nexus-raring
On 04/25/2013 03:28 AM, Sebastien Bacher wrote: Just as a small status update, since we are wrapping the raring cycle I though it would be good to have an updated snapshot, so I did one yesterday (using the current raring iso): https://wiki.ubuntu.com/Nexus7/Smem-2013-04-24 FYI: the QA team has some automated tests that produce some reports you might find interesting: http://reports.qa.ubuntu.com/memory/arch/armhf/ -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: smem report from the nexus-raring
Le 25/04/2013 18:06, Sebastien Bacher a écrit : I will follow up on the list when I have more informations Laney found an issue with glib-networking (relying on DESKTOP_SESSION=gnome for detecting the method to use, where we set it to ubuntu which shouldn't use the fallback mode either) and is working on a fix, details on https://bugs.launchpad.net/glib-networking/+bug/1172792 That will fix the ubuntu-geoip case (which does access proxy through glib), but the problem with libproxy is still there and affects signond/signon-ui which are using libproxy directly, we will need to deal with those as well Cheers, Sebastien Bacher -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: smem report from the nexus-raring
On Mon, Jan 28, 2013 at 09:06:41PM +0100, Sebastien Bacher wrote: We recently did a smem memory snapshot from raring, running on a nexus tablet. The results have been recorded on the wiki: https://wiki.ubuntu.com/Nexus7/Smem-2013-01-16 I've been spending some time trying to track down memory leaks this week. Here are a few notes. valgrind was of course the first thing I reached for. I had to fix a few things (you used to need valgrind-dbg to get useful stack traces on ARM, and a fairly common instruction wasn't implemented), so make sure you have the most current valgrind in raring. It's not perfect for desktop stuff, because it's unaware of GObject references, and because GTK+ allocates quite a few singleton structures which remain unfreed on exit; I hear refdbg can help, but I haven't tried that yet. However, if you decide you don't care about reference cycles or unfreed singletons (which I think is not necessarily a bad approach, at least to start with), the --show-possibly-lost=no option can help cut the output down to something more reasonable. I ran across https://fedorahosted.org/gdb-heap/, which is handy for figuring out something of what's going on with running processes; I'm working on packaging this, but in the meantime you can grab it from git (I think I'd recommend that over the last release, as it's gained some awareness of GTypes). You can check it out in your home directory and then do: $ sudo PYTHONPATH=/home/ubuntu/gdb-heap gdb /path/to/executable PID (gdb) python import gdbheap (gdb) heap ... then for example ... (gdb) heap select kind=string data Poking around here can give you a sense of where memory is going. I used a combination of this and valgrind to track down leaks in upower (and sorry for the regression yesterday, caused by me unwisely applying a small patch by hand); you can see the difference here: http://people.canonical.com/~j-lallement/N7/memusage/idle/upowerd.png Caches are important, and they often rely on filesystem timestamps, especially the ones that can only be built as root. Unfortunately, the Nexus 7 installer was failing to preserve timestamps, possibly due to a false-economy attempt to make the installer run more quickly. As a result, for example, anything that loaded a GTK+ icon theme was allocating several hundred KB of memory more than it needed to. We've fixed this now in the installer; if you don't want to reflash, then at least run 'sudo update-icon-caches /usr/share/icons/*'. -- Colin Watson [cjwat...@ubuntu.com] -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: smem report from the nexus-raring
Hello, On Mon, 28 Jan 2013 21:06:41 +0100, Sebastien Bacher wrote: We recently did a smem memory snapshot from raring, running on a nexus tablet. The results have been recorded on the wiki: https://wiki.ubuntu.com/Nexus7/Smem-2013-01-16 At least some of the items have notes indicating work has already started on them. Do either of these have issues filed? It would be easier to follow progress and have discussions related to individual applications' memory consumption in the familiar LP bug interface, while keeping the wiki page as an overview with links to LP. Jani -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: smem report from the nexus-raring
Le 29/01/2013 10:18, Jani Monoses a écrit : At least some of the items have notes indicating work has already started on them. Do either of these have issues filed? It would be easier to follow progress and have discussions related to individual applications' memory consumption in the familiar LP bug interface, while keeping the wiki page as an overview with links to LP. Hey Jani, Good point, I've been trying to transform the actions noted there to workitems, mostly on that spec: https://blueprints.launchpad.net/ubuntu/+spec/desktop-r-reduced-power-ram If you see any which is not listed feel free to edit the workitems list to add it ;-) Cheers, Sebastien Bacher -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
smem report from the nexus-raring
Hey everybody, Just a small update from the work ongoing with making Ubuntu fit for mobile devices [1] ;-) We recently did a smem memory snapshot from raring, running on a nexus tablet. The results have been recorded on the wiki: https://wiki.ubuntu.com/Nexus7/Smem-2013-01-16 We started adding comments to the table and converting some of those to work items. If you are interested to help there, or have any comments, feel free to either reply to this email or to put comments on the wiki Cheers, Sebastien Bacher [1] http://status.ubuntu.com/ubuntu-raring/group/topic-raring-desktop-targets-for-embedded.html -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
