| 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: | QuadEM Update rate limited by lock |
| From: | Iain Marcuson via Tech-talk <tech-talk at aps.anl.gov> |
| To: | "tech-talk at aps.anl.gov" <Tech-talk at aps.anl.gov> |
| Date: | Wed, 20 Nov 2024 16:58:39 +0000 |
|
I am writing EPICS for a QuadEM, based on designs in the distribution. The data come at 200 Hz, and my benchmarking in EPICS shows that I receive at that rate with very low jitter. Following the examples of other electrometers, I lock()
before computePositions() and callParamCallbacks(). I have observed that the lock() takes about 6 ms, which is too long for the full packet rate. Is this a normal time for the lock()? I believe I have eliminated other calls for the lock() in my code, although
a calltree shows lock()s in the callbacks. Thank you, Iain. This message has been scanned for malware by Forcepoint. www.forcepoint.com |