Fake camera performance

Hi everyone,

I’m working with Aravis and the fake camera, and I’ve run into a performance question.

When using the fake camera with a resolution of 2048x2048 mono8, I consistently hit a maximum of 25 frames per second (fps). Even if I configure it for a higher desired frame rate using arv_camera_set_frame_rate(), the actual received frame rate never exceeds 25 fps.

I’ve already confirmed that my system can handle real GigE Vision cameras at the same resolution and pixel format with no issues, achieving much higher frame rates. This suggests the bottleneck isn’t my network performance or the general capabilities of my computer to process high-speed image data.

Given this, I suspect the 25 fps limit might be an inherent limitation of the Aravis fake camera’s software-based simulation for this resolution/bit depth.

Could anyone shed some light on whether this is an expected performance ceiling for the fake camera at 2048x2048 mono8? Are there any known ways to improve its simulated frame rate, or is it simply a design constraint for a software-only implementation?

Any insights or similar experiences would be greatly appreciated!

Thanks,
Pau

Hi,

The fake camera is mostly a debugging tool. No effort was made to make it efficient.

Currently, the test image is regenerated at each frame. As it is simply a sliding image, a memory copy of a persistent buffer would probably improve things.

Patch welcome !

Emmanuel.

1 Like