NVIDIA-ISAAC-ROS / NVIDIA-ISAAC-ROS/isaac_ros_pose_estimation

Discrepancy between observed performance (1.4 Hz) and official benchmarks (4.6 QPS) for FoundationPose on Jetson Orin

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

Nobody has claimed this yet.

Dominant language
C++
Stars
501
Forks
57
PR merge metrics
No merged PRs in 30d

Description

I am running Isaac ROS FoundationPose on a Jetson Orin, but I am only achieving a pose estimation frequency of approximately 1.5 Hz. According to the official NVIDIA documentation, the performance is rated at 4.6 QPS.

I would like to clarify if the reported 4.6 QPS figure refers strictly to the forward inference latency of the refine_model and score_model. Does this benchmark exclude the computational overhead of the GXF pipeline, specifically the pre-processing (sampling and Nvdiffrast rendering) and post-processing (decoding) stages?

The following are the execution latencies for the most time-consuming stages in the pipeline:
Pose Sampling and Rendering: 420 ms
Refine Model Inference and Sync: 240 ms
Score Model Inference and Sync: 200 ms

Image Image

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 the official NVIDIA benchmark definition and the GXF pipeline stages named in the issue: Pose Sampling and Rendering, Refine Model Inference and Sync, and Score Model Inference and Sync. Compare the reported 420 ms, 240 ms, and 200 ms latencies to determine whether 4.6 QPS covers only model inference or the full pipeline; done means documenting the benchmark scope and explaining the observed 1.5 Hz result.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-vision, machine-learning, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.