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: Very slow reconnection to medm after IOC reboot |
From: | Steve Lewis <[email protected]> |
To: | "Jeff Hill" <[email protected]> |
Cc: | "'Core-Talk'" <[email protected]>, "'Mark Rivers'" <[email protected]> |
Date: | Wed, 4 Feb 2009 07:11:59 -0800 |
At 6:46 PM -0700 2009/02/03, Jeff Hill wrote:
...long discussion omitted...- How would we actually like it to behave in the future.Connect times should be as fast, and responsive to the appearance of a new IOC, as possible without impacting overall network stability, but I suspect that you are not surprised to hear that answer. I am actually quite malleable to suggestions on how we can improve performance, but system stability must be guaranteed as our first priority.
'...first priority'? I disagree.While I appreciate the need to allow large sites to ensure network stability *WITH PROPER CONFIGURATION* (and not too long ago SNS presented a convincing field case), we should also allow a knowledgeable EPICS administrator to configure a small test system to achieve the historical fast reconnect times. Both scenarios are equally important.
So my suggestion is: enable the historical behavior (using the original code?) to take effect with the proper environment variables. I could even live with conditional compilation (-DCA_BEST_RESPONSE vs -DCA_MOST_STABILITY).