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: | Re: ADVimba CPU usage |
From: | Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> |
To: | EPICS tech-talk <tech-talk at aps.anl.gov>, Sandeep Kumar Malu - STFC UKRI <sandeep-kumar.malu at stfc.ac.uk> |
Date: | Tue, 16 Jan 2024 14:35:38 +0000 |
Hi Sandeep,
Please create an issue for this problem here:
https://github.com/areaDetector/ADVimba/issues
Please provide the following:
I just did a quick test of a GC1380CH camera with ADVimba. It used 30% of 1 core when
running at 30 frames/s. I had only NDPluginPVA running. When I stopped the camera acquisition the CPU dropped to 0%, as I expected. When I selected external trigger but have no trigger pulses arriving I also get 0 frames/s and 0% CPU, as I expect.
Mark
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Sandeep Kumar Malu - STFC UKRI via Tech-talk <tech-talk at aps.anl.gov>
Sent: Tuesday, January 16, 2024 6:08 AM To: EPICS tech-talk <tech-talk at aps.anl.gov> Subject: ADVimba CPU usage
Hi All
I have been using ADVimba Areadetector driver for AVT MakoG234C (1936x1216) Cameras. 15 cameras are running with external triggers of 10 fps and the CPU usage is ~27%.
However, when I deployed those 15 cameras keeping the external trigger (from the delay generator) off, the CPU usage drastically goes up to ~75%. Also, I noticed the same behaviour when Acquire is OFF or switched to Software Trigger source.
Has anyone seen this behaviour when the driver is not actually acquiring the images? Is there any solution to this drastic CPU usage?
Many Thanks
Sandeep
|