Skip to content

docs(reid): what ReID costs in frames per second - #621

Open
AlexBodner wants to merge 6 commits into
feat/core/deep-ocsort-adaptive-fusionfrom
docs/reid-speed
Open

AlexBodner wants to merge 6 commits into
feat/core/deep-ocsort-adaptive-fusionfrom
docs/reid-speed

Conversation

@AlexBodner

@AlexBodner AlexBodner commented Oct 8, 2026 •

Copy link
Copy Markdown
Collaborator

Adds a Speed section to the ReID guide, comparing BoT-SORT without ReID, with each dataset's fine-tuned osnet_x1_0, and with the published fastreid_mot17_sbs50. Stacked on #571.

The benchmark notebook contains the benchmark code and saved outputs used for the results below. Rerunning it requires access to the benchmark inputs and fine-tuned encoders.

Dataset Split BoT-SORT (FPS) + fine-tuned OSNet (FPS) + FastReID (FPS)
MOT17 val-half 31.1 10.7 6.1
SportsMOT val 38.4 16.3 10.3
DanceTrack val 33.8 15.4 10.9
SoccerNet train 32.6 13.2 6.8

Adding the fine-tuned OSNet made tracking 2.2 to 2.9 times slower than BoT-SORT alone. Adding FastReID made it 3.1 to 5.1 times slower.

How it was measured

  • Timed tracker.update only. Frame decoding and detection parsing were outside the timed call; encoder loading happened at construction and was not timed.
  • BoT-SORT sent only high-confidence detections to the encoder. All three runs for a sequence used the same provided detections and library defaults, with camera motion compensation on. SoccerNet used ground-truth boxes, as in the Results tables.
  • Measured every sequence of each tuning split: 134 sequences and 97,880 frames. The notebook saved the first three datasets in its main run and SoccerNet in a separate completed cell.
  • The notebook setup output reports a Google Colab Tesla T4, an Intel Xeon @ 2.00GHz with 2 vCPUs, and PyTorch 2.11.0+cu130. These values replace an earlier T4 run using PyTorch 2.11.0+cu128; results from the two runs are not mixed in the table.

BoT-SORT with no ReID, with each dataset's fine-tuned osnet_x1_0 and with
fastreid_mot17_sbs50, timed over every sequence of the four tuning splits on
one Colab T4 with a 2-vCPU Xeon, at library defaults.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@AlexBodner
AlexBodner requested a review from SkalskiP as a code owner October 8, 2026 13:22
@Borda
Borda requested a balanced review from Copilot October 12, 2026 08:21
@Borda Borda added the documentation Improvements or additions to documentation label Oct 12, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The methodology incorrectly states that ReID encodes every detection rather than only high-confidence detections.

1 open finding
What changed in this PR

Adds measured ReID throughput costs to the BoT-SORT ReID guide.

Changes:

  • Documents benchmark methodology and hardware.
  • Compares FPS across four datasets and two encoders.
  • Summarizes observed throughput reductions.
File Description
docs/​guides/​reid.md Adds the ReID speed benchmark section and results.

🧠 Review effort: Balanced


💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread docs/guides/reid.md Outdated
Comment thread docs/guides/reid.md Outdated
Comment thread docs/guides/reid.md Outdated
Comment thread docs/guides/reid.md Outdated

@tstanczyk95 tstanczyk95 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AlexBodner It's a promising table, but it needs clarification. See my remarks above.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants