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: | Alarm Handler Limitations |
From: | "Srinivas, Dhruv via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Fri, 5 Apr 2024 20:34:16 +0000 |
I am currently working on creating an alarm server for our epics IOCs and I’ve been running into a few issues in the process.
To begin with, I’ve noticed that if I add a large number of alarms (~5000 or more), it causes the initial loading process to take a significant amount of time. Often on the order of 30 minutes. I was wondering if this was expected behavior
or if there are ways to reduce the load time. Secondly, I’ve had issues connecting Phoebus to the alarm server. At the moment, I have Phoebus running on one machine and the alarm server running on another one due to various limitations. I also have kafka and zookeeper running on the
same machine as the alarm server and have verified that the CLI is functioning. I was hoping someone would know how to connect Phoebus to it, as I’ve been unable to find the port it should connect to. Sincerely, Dhruv Srinivas |