Sorry about the text in the post. I wanted to give you guys something
better, so I ran perf record for a a few seconds. I then perf report
>> perf_report.
The report is attached. It might be easier to read.
Michael Knap
http://michaelknap.net
Instructor and Researcher
Mathematics and Controls Engineering
Center of Excellence in Information Systems
Tennessee State University
On Sun, Jan 29, 2012 at 10:10 PM, Michael Knap <email address hidden> wrote:
> I just wanted to say that there is seems to be no evidence of memory
> usage growing. I am not sure how a vector could be growing without
> memory growing.I guess it could be growing in a pre-allocated space,
> though. But another update... the work pc shows compiz now at 47%
> since Fri afternoon. I ran another perf top -p compizPID on it. I
> think my previous output was truncated, so here is another output with
> more info in the line. I guess this is some kind of a trace. Maybe it
> will help. Finally, I will have to restart compiz on my work pc
> tomorrow. Is there any more info anyone would like to gather while we
> have an opportunity to get to this bug ?
>
> PerfTop: 372 irqs/sec kernel: 1.9% exact: 0.0% [1000Hz
> cycles], (target_pid: 1898)
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> samples pcnt function
>
>
>
>
> DSO
> _______ _____
> __________________________________________________________________________________________________________________________________________
>
>
>
> _______________________________
>
> 5419.00 97.0% __gnu_cxx::__normal_iterator<int*,
> std::vector<int, std::allocator<int> > >
> std::__find<__gnu_cxx::__normal_iterator<int*, std::vector<int,
> std::allocator<int> > >, int>(__gnu_cxx::__normal_iterator<int*,
> std::vector<int, std::allocator<int> > >,
> __gnu_cxx::__normal_iterator<int*, std::vector<int,
> std::allocator<int> > >, int const&, std::random_access_iterator_tag)
> libnux-graphics-1.0.so.0.1600.0
>
>
> Thank you for all input and work !
>
>
> Michael Knap
>
> http://michaelknap.net
> Instructor and Researcher
> Mathematics and Controls Engineering
> Center of Excellence in Information Systems
> Tennessee State University
>
>
>
> On Sun, Jan 29, 2012 at 9:34 PM, Daniel van Vugt <email address hidden> wrote:
>> Admittedly it should probably be using std::set (find = O(lgN)) instead
>> of std::vector (find = O(N)). But we might be looking at the wrong code
>> completely...
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/888039
>>
>> Title:
>> Gradual degradation in desktop performance.
>>
>> Status in Compiz:
>> Confirmed
>> Status in “compiz” package in Ubuntu:
>> Confirmed
>>
>> Bug description:
>> Over the span of 1-3 days I see my desktop consistently become more
>> sluggish. The functions most affected are window movement, file icon
>> movement, and sometimes window resizing. Other animations (such as
>> minimizing fades, switching desktops, expo mode) are not affected when
>> this degradation occurs. They remain smooth; however, I have let the
>> problem go on as long as to find out that eventually all desktop
>> animations/effects will degrade, it just takes a lot lot longer. I
>> find that my actual 3D gaming goes unaffected (though I have no data
>> to back that up, perhaps it does).
>>
>> I have recorded the output of 'ps auxw' and have slowly watched the
>> VSZ and RSS memory columns creep upwards. A fresh compiz session will
>> see 675164 and 169860, respectively. After a day or two it will result
>> in as high as 878552 and 255664. I have attached a log output from an
>> hourly cron job (though I had suspended for a few days because of
>> travel).
>>
>> After the degradation has occurred compiz will consistently use higher
>> CPU. Dragging a terminal window while watching top: before: ~10%,
>> after: ~30 percent.
>>
>> This has been an issue since 11.04 for me on both my Intel i915 and
>> Nvidia (proprietary) machines (had an 8600 GT and upgraded to 560 GTX,
>> both having the same issue). However, the nvidia machine is where it
>> really hurts, _always_ happening within a day or two, while the i915
>> machine is pretty reliable overall with certain instances of
>> degradation (used to be affected just as badly in 11.04).
>>
>> I will attach two videos demonstrating behavior before and after.
>> ---
>> ApportVersion: 1.23-0ubuntu4
>> Architecture: amd64
>> CheckboxSubmission: 33c9cec13de798ee31ce4ea2f2cbd4df
>> CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
>> CompizPlugins: [core,detection,composite,opengl,decor,regex,winrules,compiztoolbox,animation,grid,vpswitch,snap,place,gnomecompat,resize,move,mousepoll,imgpng,workarounds,session,expo,wall,fade,scale,unityshell]
>> DistroCodename: oneiric
>> DistroRelease: Ubuntu 11.10
>> DistroVariant: ubuntu
>> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
>> NonfreeKernelModules: nvidia
>> Package: compiz 1:0.9.6+bzr20110929-0ubuntu5vv1
>> PackageArchitecture: all
>> ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
>> Tags: oneiric running-unity oneiric running-unity ubuntu
>> Uname: Linux 3.0.0-12-generic x86_64
>> UnreportableReason: This is not a genuine Ubuntu package
>> UpgradeStatus: Upgraded to oneiric on 2011-10-13 (26 days ago)
>> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/compiz/+bug/888039/+subscriptions
Sorry about the text in the post. I wanted to give you guys something
better, so I ran perf record for a a few seconds. I then perf report
>> perf_report.
The report is attached. It might be easier to read.
Michael Knap
http:// michaelknap. net
Instructor and Researcher
Mathematics and Controls Engineering
Center of Excellence in Information Systems
Tennessee State University
On Sun, Jan 29, 2012 at 10:10 PM, Michael Knap <email address hidden> wrote: ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ---- _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _____ _______ _______ _______ ___ :__normal_ iterator< int*, find<__ gnu_cxx: :__normal_ iterator< int*, std::vector<int, gnu_cxx: :__normal_ iterator< int*, :__normal_ iterator< int*, std::vector<int, access_ iterator_ tag) graphics- 1.0.so. 0.1600. 0 michaelknap. net /bugs.launchpad .net/bugs/ 888039 e31ce4ea2f2cbd4 df 7770f606350a390 a2 ,composite, opengl, decor,regex, winrules, compiztoolbox, animation, grid,vpswitch, snap,place, gnomecompat, resize, move,mousepoll, imgpng, workarounds, session, expo,wall, fade,scale, unityshell] dules: nvidia bzr20110929- 0ubuntu5vv1 ture: all ature: Ubuntu 3.0.0-12.20-generic 3.0.4 /bugs.launchpad .net/compiz/ +bug/888039/ +subscriptions
> I just wanted to say that there is seems to be no evidence of memory
> usage growing. I am not sure how a vector could be growing without
> memory growing.I guess it could be growing in a pre-allocated space,
> though. But another update... the work pc shows compiz now at 47%
> since Fri afternoon. I ran another perf top -p compizPID on it. I
> think my previous output was truncated, so here is another output with
> more info in the line. I guess this is some kind of a trace. Maybe it
> will help. Finally, I will have to restart compiz on my work pc
> tomorrow. Is there any more info anyone would like to gather while we
> have an opportunity to get to this bug ?
>
> PerfTop: 372 irqs/sec kernel: 1.9% exact: 0.0% [1000Hz
> cycles], (target_pid: 1898)
> -------
>
> samples pcnt function
>
>
>
>
> DSO
> _______ _____
> _______
>
>
>
> _______
>
> 5419.00 97.0% __gnu_cxx:
> std::vector<int, std::allocator<int> > >
> std::__
> std::allocator<int> > >, int>(__
> std::vector<int, std::allocator<int> > >,
> __gnu_cxx:
> std::allocator<int> > >, int const&, std::random_
> libnux-
>
>
> Thank you for all input and work !
>
>
> Michael Knap
>
> http://
> Instructor and Researcher
> Mathematics and Controls Engineering
> Center of Excellence in Information Systems
> Tennessee State University
>
>
>
> On Sun, Jan 29, 2012 at 9:34 PM, Daniel van Vugt <email address hidden> wrote:
>> Admittedly it should probably be using std::set (find = O(lgN)) instead
>> of std::vector (find = O(N)). But we might be looking at the wrong code
>> completely...
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https:/
>>
>> Title:
>> Gradual degradation in desktop performance.
>>
>> Status in Compiz:
>> Confirmed
>> Status in “compiz” package in Ubuntu:
>> Confirmed
>>
>> Bug description:
>> Over the span of 1-3 days I see my desktop consistently become more
>> sluggish. The functions most affected are window movement, file icon
>> movement, and sometimes window resizing. Other animations (such as
>> minimizing fades, switching desktops, expo mode) are not affected when
>> this degradation occurs. They remain smooth; however, I have let the
>> problem go on as long as to find out that eventually all desktop
>> animations/effects will degrade, it just takes a lot lot longer. I
>> find that my actual 3D gaming goes unaffected (though I have no data
>> to back that up, perhaps it does).
>>
>> I have recorded the output of 'ps auxw' and have slowly watched the
>> VSZ and RSS memory columns creep upwards. A fresh compiz session will
>> see 675164 and 169860, respectively. After a day or two it will result
>> in as high as 878552 and 255664. I have attached a log output from an
>> hourly cron job (though I had suspended for a few days because of
>> travel).
>>
>> After the degradation has occurred compiz will consistently use higher
>> CPU. Dragging a terminal window while watching top: before: ~10%,
>> after: ~30 percent.
>>
>> This has been an issue since 11.04 for me on both my Intel i915 and
>> Nvidia (proprietary) machines (had an 8600 GT and upgraded to 560 GTX,
>> both having the same issue). However, the nvidia machine is where it
>> really hurts, _always_ happening within a day or two, while the i915
>> machine is pretty reliable overall with certain instances of
>> degradation (used to be affected just as badly in 11.04).
>>
>> I will attach two videos demonstrating behavior before and after.
>> ---
>> ApportVersion: 1.23-0ubuntu4
>> Architecture: amd64
>> CheckboxSubmission: 33c9cec13de798e
>> CheckboxSystem: 4ed15c40009aa6f
>> CompizPlugins: [core,detection
>> DistroCodename: oneiric
>> DistroRelease: Ubuntu 11.10
>> DistroVariant: ubuntu
>> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
>> NonfreeKernelMo
>> Package: compiz 1:0.9.6+
>> PackageArchitec
>> ProcVersionSign
>> Tags: oneiric running-unity oneiric running-unity ubuntu
>> Uname: Linux 3.0.0-12-generic x86_64
>> UnreportableReason: This is not a genuine Ubuntu package
>> UpgradeStatus: Upgraded to oneiric on 2011-10-13 (26 days ago)
>> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>>
>> To manage notifications about this bug go to:
>> https:/