Experimental Physics and
Industrial Control System



Hi Sandeep,

Please create an issue for this problem here: https://github.com/areaDetector/ADVimba/issues

Please provide the following:

• The versions of ADCore and ADVimba
• Is this Windows or Linux?
• How many cores on the IOC machine?
• When you say 75% of the CPU do you mean 75% of a single core, or 75% of all cores?
• When you remove the external trigger what frame rate are the cameras getting?  It should be 0.
• A screenshot of the AVVimba screen when the problem is happening
• A screenshot of the commonPlugins OPI screen when the problem is happening so we can see what plugins are running and at what rate.
• A screenshot of "top -h" in the IOC computer when the problem is happening on.  This will show us what threads are using the CPU.

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