In my case, in order to download the SUSE fixpack, due to our network restrictions (something about a key is only good for 5 minutes), I would have to bring up x-windows, KDE and then Mozilla, in order to connect to the Suse website to download.
What a dog!
Neat to see that it can be done if needed.
But you are right, when it starts, it is a CPU black hole. After 5-10 minutes, it settles down to only take about 20 mips (only 20...yea).
But if you shut it down and IPL the Linux image, it takes just as long the next time. Not like some things that when it is executed the first time, it seems to do something like a compile, and saves the result (PDF files are like this). Subsequent executions bypass the "compile" step.
I'm on a MP/3000 with z/VM 4.2 and Suse 7.3 and 8.0.
Tom Duerbusch THD Consulting
David Kreuter wrote:
Hi: A client experiences intermittent significant performance slowdowns using xwindows. Environment is zvm 4.4, suse sles8 kernel 2.4.19 windows server is 6.00.191.
I was luck to catch a glimpse of this today, and from the zvm perspective the CPU of the linux server spiked from about 10% to over 80% for a few minutes, and then suddenly the lights went from dim to lit on the xwindows client.
Nothing else was running on the box at the time other than vm tcpip.
There was as far as I can tell nothing untowards happening in zvm tcpip, paging was negligible, dasd i/o was negligible.
User says it seems to happen displaying a file "for the first time". Subsequent xwindows display of the files "are faster".
IS this a caching issue in linux? Any other ideas? Thanks! David Kreuter
