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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: [EXTERNAL] phoebus display runtime |
From: | "Kasemir, Kay via Tech-talk" <tech-talk at aps.anl.gov> |
To: | tech-talk <tech-talk at aps.anl.gov>, "chenhuiting at zjlab.org.cn" <chenhuiting at zjlab.org.cn> |
Date: | Mon, 31 Oct 2022 15:25:11 +0000 |
Is everything that you describe happening on the same host, or are you remotely viewing the display via ssh/remote-X or VNC or Thinlinc or ...?
Rendering via a remote connection tends to be slower.
As long as you render locally, i.e. cs-studio is running on the host that has the actual display/mouse/keyboard, try to figure out what part of the display is causing the slowdown.
For example, delete some plots and check if that makes a difference.
Finally, once you narrowed down what is causing the slowdown, you can try running with jvisualvm or jprofiler to see where it is spending its time.
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of chenhuiting--- via Tech-talk <tech-talk at aps.anl.gov>
Sent: Monday, October 31, 2022 3:53 AM To: tech-talk <tech-talk at aps.anl.gov> Subject: [EXTERNAL] phoebus display runtime Dear,all
I have a problem that java processes always occupy too much CPU, causing the computer system to crash,while phoebus is running.
After restarting the computer or phoebus software, the system becomes smooth. However,the computer becomed sluggish after more than ten hours of uptime when phoebus’s file is display runtime. There is only one setting for address in the aile settings.ini. I have tried different versions of phoebus, but the same situation has occurred. I used jstack, top -H, and matching pid with nid to find out what is happening. I found that the culprit was QuantumRenderer with 95+% CPU usage.
The application is using a 64Bit version of centos 7 with base3-15-5. And the current version is phoebus-4.6.6 with jdk-16.0.1.
I can't figure out where should I look to find out what is the problem... How can I solve this problem?
Thanks! chenhuiting at zjlab.org.cn
CHEN Huiting Beamline Contrl Group, SSRF No. 239 Zhangheng Road, Pudong, Shanghai |