roboflow / roboflow/inference

Video Processing API - processing inside docker on Jetson is noticeably slower than bare-metal

Open
#687 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug Video Management API issues
Dominant language
Python
Stars
2.5k
Forks
319
Avg merge
1d 14h
Merged PRs (30d)
133

Description

Search before asking
  • I have searched the Inference issues and found no similar bug report.
Bug

The same workflow tested, reporting only latency for single frame processing inside WorkflowRunner.run_workflow(...) function:

Jetson Nano Orin, bare metal in script using InferencePipeline directly - not measured precisely now, but older tests indicated the same performance as on MacBook when yolov8n-640 used - which was the model used in test case
Jetson Nano Orin, inside docker container, behind API - ~50ms
We have docker overhead, not 100% sure if it is visible on Jetson devices, but MacBook one makes drop from 27fps into <10fps 😢

Also measured that running 2 streams at the time gives over 30FPS in total so the compute is there, but something makes the pipeline slower than potentially could be inside Jetson Docker

Environment

Jetson Nano Orin, Jetpack 5.1.1

Minimal Reproducible Example

No response

Additional

No response

Are you willing to submit a PR?
  • Yes I'd like to help by submitting a PR!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with inference/core/interfaces/stream/model_handlers/workflows.py and the WorkflowRunner.run_workflow(...) path, then reproduce the single-frame latency comparison on Jetson Nano Orin with JetPack 5.1.1 in bare-metal and Docker environments. Done means the container slowdown is explained and the processing performance is improved or the relevant limitation is documented with measured results.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, python
Domain
computer-vision, devops, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.