| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 <2006> 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 <2006> 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | RE: StripTool bogs down host? |
| From: | "Chu, Paul C." <[email protected]> |
| To: | Chris Payne <[email protected]>, John Dobbins <[email protected]> |
| Cc: | EPICS Tech-Talk <[email protected]> |
| Date: | Wed, 26 Apr 2006 17:24:01 -0400 |
Hi,
We used to have Matrox G450 video cards with Xinerama only (6-head
display using 2 quad-head G450) and it was a lot easier to get up to
upper 90% CPU loading with StripTool chart(s) running or even to crash
the console. Switching to nVidia video cards (GeForce FX5500, Quadro
NVS280, etc.) with a combination of twinView and Xinerama (3 twinView's)
helps to reduce the problem a lot. The overall performance is a
combination of hardware (video card), X server, physical memory size and
display buffer size.
Also, some people want to use StripTool as archiver -- with a very large
buffer and save the buffered data to a file. I don't think this is a
very good idea. Maybe the default StripTool buffer size should be
smaller and have a hard limit for the buffer?
Paul
Paul C. Chu
Accelerator Physics
Spallation Neutron Source
Oak Ridge National Laboratory
-----Original Message-----
From: Chris Payne [mailto:[email protected]]
Sent: Wednesday, April 26, 2006 4:32 PM
To: John Dobbins
Cc: EPICS Tech-Talk
Subject: Re: StripTool bogs down host?
John--
We have seen response exactly like this, a relatively powerful Linux
computer
"bogged down" by a single StripTool, and it was definitely made worse by
increasing the graph window size. Our operations staff subsequently
learned
the "don't do that" rule.
Since the initial problems, we have gone through many upgrades, OS,
EPICS
base, extensions, and now I cannot seem to reproduce the problem on our
present consoles.
The problem was obvious on RedHat 7.2 with stock XFree86 and extensions
compiled against 3.13.5-ish (I think) and whatever X libraries (lesstif
maybe?) were there. Hardware was dual P3 1GHz with old ATI cards.
We are now on Scientific Linux 4.2 with stock Xorg, but an NVidia driver
for
the NVS400 cards we use. The extensions are compiled against 3.13.10,
and the
installed libraries (openmotif 2.2.3). Hardware is a P4 3.2GHz with the
NVidia card.
I think that the upgrade to the X server and new libraries are what did
it for
us, but I'm not 100% sure. How up to date are your OS and Libraries?
Cheers
Chris
--
Chris Payne ISAC Operations Controls System Manager
"Relax Snap, this is particle physics, not rocket science."
On Tue, Apr 25, 2006 at 01:35:34PM -0400, John Dobbins wrote:
> We've begun using StripTool and notice that is sometimes appears to
bog
> down the computer on which it is running, i.e. the mouse responds
haltingly
> with StripTool running, there is lag in button responses,...
>
> This is true even if StripTool is the only app running. Host is Linux.
>
> It seems to be made worse by making the StripTool graph display larger
and
> helped by reducing the screen update rate.
>
> Do others have this experience? I looked in the docs and searched
Tech-Talk
> but didn't see anything along these lines. Is something that can be
done to
> improve responsiveness?