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: | CSS 4.1: performance drop when using linking container and macros |
From: | "Zumbruch, Peter Dr." <[email protected]> |
To: | "[email protected]" <[email protected]> |
Date: | Fri, 4 Mar 2016 11:19:14 +0000 |
Hi, from a different setup I got a monolithic .opi-File for the control of a HV crate. (see ISEG_HV_monolithic.tar.gz) For a better maintenance I rewrote it and split it up into single opi Files which are then included by linking container widgets and configuring them using macros. By this “RICH_HV_2016.opi” includes
1 time “HV_16x10.opi” which itself links
10 times “HV_16ch_set.opi ” which again itself links
17 times “HV_Channel.opi“. (see ISEG_HV_modular.tar.gz) Simply comparing the file sizes and the lines of code I came down from 4.5 MB and ~115.000 lines down to 152kB and ~4300 lines. But, comparing the startup times (just counting the seconds) I see a difference of a factor of ~5, where the monolithic opi just took 1-2 seconds to come up. Also the connection time to the see the variables slowed significantly down. Is this a bad strategy / ansatz? In general how to determine the performance more objectively?
Any comments welcome. Best regards, Peter -- |
Attachment:
ISEG_HV_monolith.tar.gz
Description: ISEG_HV_monolith.tar.gz
Attachment:
ISEG_HV_modular.tar.gz
Description: ISEG_HV_modular.tar.gz