On Wed, 2009-01-21 at 10:54 +0100, John Clarke wrote: > > > The above indicates this is due to the 'isis' process, not X? > > Is that possible? isis is my big number-crunching task - I/O from > files and very occasional (every 20 seconds or so) printf()s to show > progress. Absolutely no X calls - not even linked to the X libraries. > How could that be hammering Xorg? Moreover Xorg's memory usage seems > a little extreme -- 400MB? My screen is otherwise idle.
I was referring to the top output, but I realize now that probably isn't representative of the problem. > So far Xorg has clocked up nearly a day of CPU time - that's an extra > day I'm waiting for my results, so the current setup is unacceptable. > > Can someone please let me know how to enable more logging, or some > other way to debug this. I'm not sure there's any logging that could help here, you're probably better off seeing where the X server process is burning cycles using a system profiler like sysprof or oprofile. -- Earthling Michel Dänzer | http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer _______________________________________________ xorg mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/xorg
