Re: gnome-shell cpu usage during installation
On Jun 21, 2013, at 11:41 AM, drago01 drag...@gmail.com wrote: This is completely irrelevant. If you want to find out whats going on install debug info packages for gnome-shell, mutter, clutter, cogl, mesa and X. Install sysprof and run sysprof to see where the cpu time is spent. OK. https://dl.dropboxusercontent.com/u/3253801/sysprof_f19gs_ffdrag If I'm reading this correctly the functions contributing to CPU usage the most, in order: _raw_spin_unlock_irqrestore called mostly by nv84_graph_tlb_flush __schedule called mostly by sys_sched_yield I'm not sure what any of that means. And I'm also not sure if that's the bulk of the difference between F18 and F19 without profiling F18 also, because I don't know if the usage amounts of those functions is normal. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On Jun 20, 2013, at 6:47 PM, Adam Williamson awill...@redhat.com wrote: It's not a general issue, I don't think. Confirming John's report, on my desktop (9600 GT), CPU usage of Shell when I'm not touching the keyboard is 0.7%, and it never goes above 3% in light desktop use. On the newer laptop it's 1-7% with either F18 or F19. On the older laptop it's 10-20% with F18 and OS X, and 70-100% with F19. All above boots are EFI. On Jun 20, 2013, at 6:45 PM, Adam Williamson awill...@redhat.com wrote: if you run it from a terminal inside the X session it should work, but if you run it from a VT, you have to do it like this: DISPLAY=:0 glxinfo | grep render F18: direct rendering: Yes OpenGL renderer string: Gallium 0.4 on NV84 GL_NV_conditional_render, GL_AMD_conservative_depth, F19: direct rendering: Yes OpenGL renderer string: Gallium 0.4 on NV84 GL_MESA_texture_signed_rgba, GL_NV_conditional_render, GL_NV_depth_clamp, GL_MESA_window_pos, GL_NV_blend_square, GL_NV_conditional_render, -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On Jun 21, 2013, at 9:56 AM, Chris Murphy li...@colorremedies.com wrote: F19: direct rendering: Yes OpenGL renderer string: Gallium 0.4 on NV84 GL_MESA_texture_signed_rgba, GL_NV_conditional_render, GL_NV_depth_clamp, GL_MESA_window_pos, GL_NV_blend_square, GL_NV_conditional_render, I'm unsure what it means for GL_NV_conditional_render to be listed twice, and for GL_AMD_conservative_depth to be listed for F18 but not F19. It looks like conservative_depth is an optimization, but I have no idea if it matters to gnome-shell. http://www.opengl.org/registry/specs/AMD/conservative_depth.txt Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On Fri, 2013-06-21 at 19:41 +0200, drago01 wrote: On Fri, Jun 21, 2013 at 6:14 PM, Chris Murphy li...@colorremedies.com wrote: On Jun 21, 2013, at 9:56 AM, Chris Murphy li...@colorremedies.com wrote: F19: direct rendering: Yes OpenGL renderer string: Gallium 0.4 on NV84 GL_MESA_texture_signed_rgba, GL_NV_conditional_render, GL_NV_depth_clamp, GL_MESA_window_pos, GL_NV_blend_square, GL_NV_conditional_render, I'm unsure what it means for GL_NV_conditional_render to be listed twice, and for GL_AMD_conservative_depth to be listed for F18 but not F19. It looks like conservative_depth is an optimization, but I have no idea if it matters to gnome-shell. http://www.opengl.org/registry/specs/AMD/conservative_depth.txt This is completely irrelevant. Yes, well, we were only looking for the 'Gallium 0.4 on XX' bit to check whether he'd somehow wound up on software rendering on F19. Obviously he hasn't. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On Fri, Jun 21, 2013 at 7:47 PM, Adam Williamson awill...@redhat.com wrote: On Fri, 2013-06-21 at 19:41 +0200, drago01 wrote: On Fri, Jun 21, 2013 at 6:14 PM, Chris Murphy li...@colorremedies.com wrote: On Jun 21, 2013, at 9:56 AM, Chris Murphy li...@colorremedies.com wrote: F19: direct rendering: Yes OpenGL renderer string: Gallium 0.4 on NV84 GL_MESA_texture_signed_rgba, GL_NV_conditional_render, GL_NV_depth_clamp, GL_MESA_window_pos, GL_NV_blend_square, GL_NV_conditional_render, I'm unsure what it means for GL_NV_conditional_render to be listed twice, and for GL_AMD_conservative_depth to be listed for F18 but not F19. It looks like conservative_depth is an optimization, but I have no idea if it matters to gnome-shell. http://www.opengl.org/registry/specs/AMD/conservative_depth.txt This is completely irrelevant. Yes, well, we were only looking for the 'Gallium 0.4 on XX' bit to check whether he'd somehow wound up on software rendering on F19. Obviously he hasn't. I know I was referring to the talk about the extensions. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On 06/19/2013 07:47 PM, Chris Murphy wrote: On Jun 19, 2013, at 8:44 PM, John Reiser jrei...@bitwagon.com wrote: On 06/19/2013 06:04 PM, Chris Murphy wrote: Hmm, neither the Fedora 18 or 19 Xorg.0.logs contain 'software renderer' or 'llvmpipe'. https://dl.dropboxusercontent.com/u/3253801/F18_Xorg.0.log https://dl.dropboxusercontent.com/u/3253801/F19_Xorg.0.log For 'glxinfo' on both F18 and 19 live media, I get Error: unable to open display. Running Fedora-Live-Desktop-i686-19-TC3-1.iso with (lspci -nn) 05:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 8400 GS Rev. 3] [10de:10c3] (rev a2) then I see 98% or more idle on a 2.0GHz Athlon 64. My Xorg.0.log is http://ur1.ca/ednn9 - http://paste.fedoraproject.org/19780/69567113 From a Terminal (gnome-terminal): $ glxinfo | grep renderer OpenGL renderer string: Gallium 0.4 on NVA8 From your Xorg log, I'm not seeing why glxinfo works for you but doesn't work for me. But for that matter I don't see why gnome-shell is using so much more CPU with F19 than F18. It doesn't seem to be nouveau related, or at least Xorg isn't revealing what the issue is. I changed to an older 8400 GS card, and using Fedora-19-Final-TC6-i386-DVD.iso. It still works for me: $ lspci -nn | grep VGA 05:00.0 VGA compatible controller [0300]: NVIDIA Corporation G84 [GeForce 8400 GS] [10de:0404] (rev a1) $ glxinfo | grep renderer OpenGL renderer string: Gallium 0.4 on NV84 The Xorg.0.log is: http://ur1.ca/eduoc - http://paste.fedoraproject.org/19940/17472281 I'm beginning to suspect an interaction between the driver and your specific hardware: chip 10de:0407 in a MacBookPro. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On Wed, 2013-06-19 at 18:34 -0600, Chris Murphy wrote: On Jun 19, 2013, at 5:17 PM, drago01 drag...@gmail.com wrote: On Thu, Jun 20, 2013 at 1:00 AM, Chris Murphy li...@colorremedies.com wrote: On Jun 19, 2013, at 3:53 PM, John Reiser jrei...@bitwagon.com wrote: Is there a more definitive way to tell if gnome-shell is or isn't offloading onto the GPU? $ glxinfo | grep renderer OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.3, 128 bits) llvmpipe is the software CPU (SSE2) renderer OpenGL renderer string: Gallium 0.4 on AMD REDWOOD One of the hardware renderers. Fedora 18: [root@localhost ~]# glxinfo | grep renderer Error: unable to open display 1. You don't have to do it as root 2. X has to be running I tried it as liveuser and root, and X is running. if you run it from a terminal inside the X session it should work, but if you run it from a VT, you have to do it like this: DISPLAY=:0 glxinfo | grep render -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On Wed, 2013-06-19 at 20:47 -0600, Chris Murphy wrote: On Jun 19, 2013, at 8:44 PM, John Reiser jrei...@bitwagon.com wrote: On 06/19/2013 06:04 PM, Chris Murphy wrote: Hmm, neither the Fedora 18 or 19 Xorg.0.logs contain 'software renderer' or 'llvmpipe'. https://dl.dropboxusercontent.com/u/3253801/F18_Xorg.0.log https://dl.dropboxusercontent.com/u/3253801/F19_Xorg.0.log For 'glxinfo' on both F18 and 19 live media, I get Error: unable to open display. Running Fedora-Live-Desktop-i686-19-TC3-1.iso with (lspci -nn) 05:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 8400 GS Rev. 3] [10de:10c3] (rev a2) then I see 98% or more idle on a 2.0GHz Athlon 64. My Xorg.0.log is http://ur1.ca/ednn9 - http://paste.fedoraproject.org/19780/69567113 From a Terminal (gnome-terminal): $ glxinfo | grep renderer OpenGL renderer string: Gallium 0.4 on NVA8 From your Xorg log, I'm not seeing why glxinfo works for you but doesn't work for me. But for that matter I don't see why gnome-shell is using so much more CPU with F19 than F18. It doesn't seem to be nouveau related, or at least Xorg isn't revealing what the issue is. It's not a general issue, I don't think. Confirming John's report, on my desktop (9600 GT), CPU usage of Shell when I'm not touching the keyboard is 0.7%, and it never goes above 3% in light desktop use. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On Jun 18, 2013, at 1:38 PM, Michael Cronenworth m...@cchtml.com wrote: On 06/18/2013 01:27 PM, Chris Murphy wrote: With the system installed, dragging e.g. a Firefox window, around the screen approximates the same behavior. gnome-shell is pegged. This doesn't seem right. The system I am typing from has the NVIDIA binary driver and experiences the same pegged behavior. Gnome Shell has always worked this way. Not for me. On a 2011 Macbook Pro I don't get either the anaconda or Firefox induced gnome-shell pegging behavior. It uses at most 7% CPU on that system, which has both MD Radeon HD 6750M and Intel HD Graphics 3000. I'm not sure which one is being used. So on the originally reported hardware with NVIDIA card, this excessive CPU usage with gnome-shell is not reproducible with Fedora 18 live media. It appears to be a new problem. Combined with the 60%-80% CPU consumption of yumbackend.py on first boot after installation of F19 for about 30 minutes while it downloads updates without my permission, the resulting sluggish behavior of the system isn't exactly the most positive initial experience. Is there a more definitive way to tell if gnome-shell is or isn't offloading onto the GPU? Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
Is there a more definitive way to tell if gnome-shell is or isn't offloading onto the GPU? $ glxinfo | grep renderer OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.3, 128 bits) llvmpipe is the software CPU (SSE2) renderer OpenGL renderer string: Gallium 0.4 on AMD REDWOOD One of the hardware renderers. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
Is there a more definitive way to tell if gnome-shell is or isn't offloading onto the GPU? During installation, look in /tmp/X.log for which modules get loaded. Here is what I see during install for [R200] [RV280] (PCI 1002:5960) Radeon 9250 (9200 PRO) where the installed Gnome3 system will try to use llvmpipe: [48.510] (EE) AIGLX error: dlopen of /usr/lib/dri/r200_dri.so failed (/usr/lib/dri/r200_dri.so: cannot open shared object file: No such file or directory) [48.510] (EE) AIGLX: reverting to software rendering [48.510] (II) AIGLX: Screen 0 is not DRI capable [48.510] (EE) AIGLX error: dlopen of /usr/lib/dri/swrast_dri.so failed (/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory) [48.510] (EE) GLX: could not load software renderer [48.510] (II) GLX: no usable GL providers found for screen 0 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On Jun 19, 2013, at 3:53 PM, John Reiser jrei...@bitwagon.com wrote: Is there a more definitive way to tell if gnome-shell is or isn't offloading onto the GPU? $ glxinfo | grep renderer OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.3, 128 bits) llvmpipe is the software CPU (SSE2) renderer OpenGL renderer string: Gallium 0.4 on AMD REDWOOD One of the hardware renderers. Fedora 18: [root@localhost ~]# glxinfo | grep renderer Error: unable to open display Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On Thu, Jun 20, 2013 at 1:00 AM, Chris Murphy li...@colorremedies.com wrote: On Jun 19, 2013, at 3:53 PM, John Reiser jrei...@bitwagon.com wrote: Is there a more definitive way to tell if gnome-shell is or isn't offloading onto the GPU? $ glxinfo | grep renderer OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.3, 128 bits) llvmpipe is the software CPU (SSE2) renderer OpenGL renderer string: Gallium 0.4 on AMD REDWOOD One of the hardware renderers. Fedora 18: [root@localhost ~]# glxinfo | grep renderer Error: unable to open display 1. You don't have to do it as root 2. X has to be running -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On Jun 19, 2013, at 5:17 PM, drago01 drag...@gmail.com wrote: On Thu, Jun 20, 2013 at 1:00 AM, Chris Murphy li...@colorremedies.com wrote: On Jun 19, 2013, at 3:53 PM, John Reiser jrei...@bitwagon.com wrote: Is there a more definitive way to tell if gnome-shell is or isn't offloading onto the GPU? $ glxinfo | grep renderer OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.3, 128 bits) llvmpipe is the software CPU (SSE2) renderer OpenGL renderer string: Gallium 0.4 on AMD REDWOOD One of the hardware renderers. Fedora 18: [root@localhost ~]# glxinfo | grep renderer Error: unable to open display 1. You don't have to do it as root 2. X has to be running I tried it as liveuser and root, and X is running. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On Jun 19, 2013, at 4:45 PM, John Reiser jrei...@bitwagon.com wrote: Is there a more definitive way to tell if gnome-shell is or isn't offloading onto the GPU? During installation, look in /tmp/X.log for which modules get loaded. Here is what I see during install for [R200] [RV280] (PCI 1002:5960) Radeon 9250 (9200 PRO) where the installed Gnome3 system will try to use llvmpipe: [48.510] (EE) AIGLX error: dlopen of /usr/lib/dri/r200_dri.so failed (/usr/lib/dri/r200_dri.so: cannot open shared object file: No such file or directory) [48.510] (EE) AIGLX: reverting to software rendering [48.510] (II) AIGLX: Screen 0 is not DRI capable [48.510] (EE) AIGLX error: dlopen of /usr/lib/dri/swrast_dri.so failed (/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory) [48.510] (EE) GLX: could not load software renderer [48.510] (II) GLX: no usable GL providers found for screen 0 Hmm, neither the Fedora 18 or 19 Xorg.0.logs contain 'software renderer' or 'llvmpipe'. https://dl.dropboxusercontent.com/u/3253801/F18_Xorg.0.log https://dl.dropboxusercontent.com/u/3253801/F19_Xorg.0.log For 'glxinfo' on both F18 and 19 live media, I get Error: unable to open display. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On 06/19/2013 06:04 PM, Chris Murphy wrote: Hmm, neither the Fedora 18 or 19 Xorg.0.logs contain 'software renderer' or 'llvmpipe'. https://dl.dropboxusercontent.com/u/3253801/F18_Xorg.0.log https://dl.dropboxusercontent.com/u/3253801/F19_Xorg.0.log For 'glxinfo' on both F18 and 19 live media, I get Error: unable to open display. Running Fedora-Live-Desktop-i686-19-TC3-1.iso with (lspci -nn) 05:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 8400 GS Rev. 3] [10de:10c3] (rev a2) then I see 98% or more idle on a 2.0GHz Athlon 64. My Xorg.0.log is http://ur1.ca/ednn9 - http://paste.fedoraproject.org/19780/69567113 From a Terminal (gnome-terminal): $ glxinfo | grep renderer OpenGL renderer string: Gallium 0.4 on NVA8 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On Jun 19, 2013, at 8:44 PM, John Reiser jrei...@bitwagon.com wrote: On 06/19/2013 06:04 PM, Chris Murphy wrote: Hmm, neither the Fedora 18 or 19 Xorg.0.logs contain 'software renderer' or 'llvmpipe'. https://dl.dropboxusercontent.com/u/3253801/F18_Xorg.0.log https://dl.dropboxusercontent.com/u/3253801/F19_Xorg.0.log For 'glxinfo' on both F18 and 19 live media, I get Error: unable to open display. Running Fedora-Live-Desktop-i686-19-TC3-1.iso with (lspci -nn) 05:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 8400 GS Rev. 3] [10de:10c3] (rev a2) then I see 98% or more idle on a 2.0GHz Athlon 64. My Xorg.0.log is http://ur1.ca/ednn9 - http://paste.fedoraproject.org/19780/69567113 From a Terminal (gnome-terminal): $ glxinfo | grep renderer OpenGL renderer string: Gallium 0.4 on NVA8 From your Xorg log, I'm not seeing why glxinfo works for you but doesn't work for me. But for that matter I don't see why gnome-shell is using so much more CPU with F19 than F18. It doesn't seem to be nouveau related, or at least Xorg isn't revealing what the issue is. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On Mon, 2013-06-17 at 19:23 -0600, Chris Murphy wrote: While anaconda is running an installation, gnome-shell is hogging a whole core on its own, and X is using about 25% of the other core. Is this expected? This is on baremetal, with a nouveau supported GPU: NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407]. I wouldn't expect gnome-shell to need to fall back to a rendering method that'd be this CPU intensive. I assume you mean the live installer by this, as the normal anaconda doesn't run gnome-shell at all. A compositor has some of the same properties as the X server itself: it _has_ to respond when an app draws something, otherwise the bits don't show up on the screen. So it's possible that what you're seeing there is anaconda updating the screen often (more than 60fps, at least), and X and the shell struggling to keep up. But this is what profilers are for. - ajax -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
While anaconda is running an installation, gnome-shell is hogging a whole core on its own, and X is using about 25% of the other core. Is this expected? This is on baremetal, with a nouveau supported GPU: NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407]. I wouldn't expect gnome-shell to need to fall back to a rendering method that'd be this CPU intensive. If I try to do this in KVM (2x CPU), I see gnome-shell taking 5%, X not even displayed in top, and all CPU power going to rsync (2x 10%) and loop3 (80%). I guess the high X+gnome-shell usage is caused by the nouveau driver. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On 06/18/2013 06:25 AM, Adam Jackson wrote: On Mon, 2013-06-17 at 19:23 -0600, Chris Murphy wrote: While anaconda is running an installation, gnome-shell is hogging a whole core on its own, and X is using about 25% of the other core. Is this expected? This is on baremetal, with a nouveau supported GPU: NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407]. I wouldn't expect gnome-shell to need to fall back to a rendering method that'd be this CPU intensive. I assume you mean the live installer by this, as the normal anaconda doesn't run gnome-shell at all. A compositor has some of the same properties as the X server itself: it _has_ to respond when an app draws something, otherwise the bits don't show up on the screen. So it's possible that what you're seeing there is anaconda updating the screen often (more than 60fps, at least), and X and the shell struggling to keep up. But this is what profilers are for. - ajax I did a pxeboot install of today's rsync using the anaconda from TC5. I ran top(1) during the install and did not notice any unusual CPU utilization. This is on a 32 GB 3770K. -- Chuck Forsberg WA7KGX c...@omen.com www.omen.com Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc The High Reliability Software 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
If I try to do this in KVM (2x CPU), I see gnome-shell taking 5%, X not even displayed in top, and all CPU power going to rsync (2x 10%) and loop3 (80%). Please tell us how much virtual RAM was allocated to the KVM instance. loop3 at 80% CPU for long periods is page thrashing: re-decompressing parts of the .exe over and over because the resulting pages are discarded too quickly. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
I did a pxeboot install of today's rsync using the anaconda from TC5. I ran top(1) during the install and did not notice any unusual CPU utilization. This is on a 32 GB 3770K. Which video graphics card, and which driver? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On Jun 18, 2013, at 7:25 AM, Adam Jackson a...@redhat.com wrote: On Mon, 2013-06-17 at 19:23 -0600, Chris Murphy wrote: While anaconda is running an installation, gnome-shell is hogging a whole core on its own, and X is using about 25% of the other core. Is this expected? This is on baremetal, with a nouveau supported GPU: NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407]. I wouldn't expect gnome-shell to need to fall back to a rendering method that'd be this CPU intensive. I assume you mean the live installer by this, Yes this is occurring with Fedora-Live-Desktop-x86_64-19-TC3-1.iso So it's possible that what you're seeing there is anaconda updating the screen often (more than 60fps, at least), and X and the shell struggling to keep up. With the system installed, dragging e.g. a Firefox window, around the screen approximates the same behavior. gnome-shell is pegged. This doesn't seem right. But this is what profilers are for. OK? Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On Jun 18, 2013, at 12:22 PM, John Reiser jrei...@bitwagon.com wrote: If I try to do this in KVM (2x CPU), I see gnome-shell taking 5%, X not even displayed in top, and all CPU power going to rsync (2x 10%) and loop3 (80%). Please tell us how much virtual RAM was allocated to the KVM instance. loop3 at 80% CPU for long periods is page thrashing: re-decompressing parts of the .exe over and over because the resulting pages are discarded too quickly. I have the same issue with loop3 on baremetal, it's variable between 45-80% CPU. 4GB RAM on that computer. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On 06/18/2013 01:27 PM, Chris Murphy wrote: With the system installed, dragging e.g. a Firefox window, around the screen approximates the same behavior. gnome-shell is pegged. This doesn't seem right. The system I am typing from has the NVIDIA binary driver and experiences the same pegged behavior. Gnome Shell has always worked this way. But this is what profilers are for. OK? You are free to profile gnome-shell and see exactly why so much CPU is used to move a window around. Maybe you could provide a patch to Gnome to reduce it. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On Jun 18, 2013, at 1:38 PM, Michael Cronenworth m...@cchtml.com wrote: On 06/18/2013 01:27 PM, Chris Murphy wrote: With the system installed, dragging e.g. a Firefox window, around the screen approximates the same behavior. gnome-shell is pegged. This doesn't seem right. The system I am typing from has the NVIDIA binary driver and experiences the same pegged behavior. Gnome Shell has always worked this way. Not for me. On a 2011 Macbook Pro I don't get either the anaconda or Firefox induced gnome-shell pegging behavior. It uses at most 7% CPU on that system, which has both MD Radeon HD 6750M and Intel HD Graphics 3000. I'm not sure which one is being used. On the older hardware with NVIDIA card, OS X's compositor doesn't have this issue with the NVIDIA produced native driver. During gnome 3's life, testing on this hardware, I intermittantly get messages of Gnome starting in fall back mode, even though it shouldn't have to do that on this hardware. So I wonder if effectively I'm getting whatever the new fallback mode CPU based compositor is. But this is what profilers are for. OK? You are free to profile gnome-shell and see exactly why so much CPU is used to move a window around. Maybe you could provide a patch to Gnome to reduce it. Maybe when I have the interest level and spare time to gain the prerequisite of knowing how to write code, and then specifically for gnome, yes maybe I can provide a patch … by which time I won't care much at all about the hardware in question. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
gnome-shell cpu usage during installation
While anaconda is running an installation, gnome-shell is hogging a whole core on its own, and X is using about 25% of the other core. Is this expected? This is on baremetal, with a nouveau supported GPU: NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407]. I wouldn't expect gnome-shell to need to fall back to a rendering method that'd be this CPU intensive. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
