# SDK 1.3.3 voxl-inspect-cam -a latency bug, inspecting large stream

Source: https://forum.modalai.com/topic/3835/sdk-1-3-3-voxl-inspect-cam-a-latency-bug-inspecting-large-stream
Category: VOXL SDK and Software (https://forum.modalai.com/category/47/voxl-sdk-and-software)
Tags: voxl-sdk
Posted: 2024-09-27 17:42:31 UTC by John Nomikos
Replies: 2 · Views: 773

## John Nomikos · 2024-09-27 17:42:31 UTC

Good afternoon,

I discovered an issue that particularly happens when you do ```voxl-inspect-cam -a```.

Upon inspecting all cams, latency jumps dramatically and continues to slowly rise. It seems to cap out right before 1000. The latency reading appears accurate because the video itself also becomes stuttery and delayed on voxl-portal.

Upon further investigation, latency also jumps when inspecting just the hires_large_color stream, or the hires_large_grey streams. But it jumps less than if you inspect all the cams at once. 

hires_small_grey, hires_small_color, and hires_small_encoded do not appear to increase in latency upon inspecting them, except if a large stream is being inspected.

Video showing what I am seeing:
https://drive.google.com/file/d/12jBzO54E5ibzsq-t-Q96cDMkEHvysYME/view?usp=sharing

## Reply by Alex Kushleyev (ModalAI staff) · 2024-10-04 02:55:42 UTC

@John-Nomikos , I think something is off with your setup, because even the small encoded stream cannot achieve 30fps. I just did a quick test on my voxl2, able to maintain 30fps in this stress test.

![d90684e2-4d71-4337-afea-d8acaf24eb3f-image.png](https://forum.modalai.com/assets/uploads/files/1728010207034-d90684e2-4d71-4337-afea-d8acaf24eb3f-image.png) 

Something is bogging down the system, you should look at output of `top` to see if there is some other process that is using up a lot of cpu.

If you cannot figure out the cause, please any other info that might help about your setup, anything non-standard that you might be using in `voxl-camera-server`.

Alex

## Reply by John Nomikos · 2024-10-04 21:46:24 UTC (in reply to Alex Kushleyev)

@Alex-Kushleyev I tried on a fresh VOXL2 that I factory flashed with 1.3.3 and did not see the same issue. Was probably something caused by my setup (either in config or something else). I know that particular voxl2 had damage to one of the mipi ports too

I appreciate the help!