Experimental Physics and
Industrial Control System
| 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 <2019> 2020 2021 2022 2023 2024 | Index | 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: Runtime slowness in CSS 3.2.16 to CSS 4.5.0 OPI project migration |
| From: | "Kasemir, Kay via Core-talk" <[email protected]> |
| To: | "[email protected]" <[email protected]> |
| Date: | Tue, 3 Sep 2019 13:47:05 +0000 |
|
Hi:
As displays grow and contain more elements which update in response to PV data, there will of course be some increase in CPU and memory usage. Still, the situation that you describe should be a little better when you move from BOY opis in CS-Studio under Eclipse to Display Builder screens with CS-Studio under Phoebus, i.e. without Eclipse.
> panels that are linked through linking containers BOY will load the content of each linking container in turn on the UI thread, i.e. everything freezes until all the content has been loaded. The Display Builder has from the start been designed to be more multithreaded. Each embedded display it loaded in background threads, in parallel. There tends to be no freezeup. You simply see an initially empty display and then the embedded content starts to show up as it's loaded.
> bigger main OPI that contains tabbed panels
When you use plain tabs, the content of each tab is "running", i.e. using CPU and memory, even though nobody is looking at it.
The Display Builder offers very similar looking "Navigation Tabs" which only load & run the currently selected tab. The other tabs use zero CPU and resources.
As to why you might see a degradation between CSS 3.2.16 to 4.5.0: CS-Studio used to be based on Eclipse, and Eclipse has grown from 3 to 4 by adding a whole new 'model' layer. Plus the build system has grown from having a CS-Studio compilation take ~20
minutes to ~45 minutes, and since about May we've been trying to update the build to work with the more recent Java 9-12 releases. Efforts are ongoing, only some sites are even able to compile it at all.
==> Your basic options are to stay with 3.2.16 if that was good enough for you, or update to the 'Phoebus' version of CS-Studio that no longer uses Eclipse, so it's quite a bit leaner, and the Display Builder, which was specifically designed
to overcome the embedded display and tab issues that you mention.
See presentations at the EPICS meetings and https://controlssoftware.sns.ornl.gov/css_phoebus/
Thanks,
Kay
From: [email protected] <[email protected]> on behalf of Lopez Antonio Miguel via Core-talk <[email protected]>
Sent: Tuesday, September 3, 2019 7:44 AM To: [email protected] <[email protected]> Subject: [EXTERNAL] Runtime slowness in CSS 3.2.16 to CSS 4.5.0 OPI project migration Hi to all!,
I'm involved on a OPI migration from CSS 3.2.16 to 4.5.0 version. This OPI set was originally developed on CSS 3.2.16, and has been growing and growing for years to the point that the performance of the OPI set is really low. I mention OPI set because the architecture is based on various panels that are linked through linking containers and macros to a bigger main OPI that contains tabbed panels depending of the system you want to control.
The main problem I'm having is the delay I'm getting when I try to open the main OPIs (the ones with the bunch linking containers) with CSS 4.5.0, even with half of the original panels. For example, a main OPI that usually takes 2 minutes after opening it to be usable in 3.2.16, takes about 5 minutes to open in 4.5.0.
In contrast, once the OPI is opened and is usable, the use of CPU in 4.5.0 remains almost constant in 7-8%, which is good, because in 3.2.16 the constant use of CPU was around 60-70%, the behavior we wanted to avoid with this migration…
Does anyone have any ideas or tests I can do to avoid this slowness when opening or refreshing the OPIs in 4.5.0?
Thanks in advance!
A. Miguel
|
- References:
- Runtime slowness in CSS 3.2.16 to CSS 4.5.0 OPI project migration Lopez Antonio Miguel via Core-talk
- Navigate by Date:
- Prev: Build failed: EPICS Base base-7.0-425 AppVeyor via Core-talk
- Next: Re: Help J. Lewis Muir via Core-talk
- Index: 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 <2019> 2020 2021 2022 2023 2024
- Navigate by Thread:
- Prev: Runtime slowness in CSS 3.2.16 to CSS 4.5.0 OPI project migration Lopez Antonio Miguel via Core-talk
- Next: Build failed: EPICS Base base-7.0-425 AppVeyor via Core-talk
- Index: 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 <2019> 2020 2021 2022 2023 2024
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·