Is BoT-SORT faster than TrackTrack?

On an NVIDIA H100 with yolo26n.pt, BoT-SORT ran at 10 FPS and TrackTrack at 14 FPS end to end, detection included. Across all 10 GPU tiers BoT-SORT was ahead on 0 and TrackTrack on 10. The ordering is the same on every tier tested.

Which holds object IDs better, BoT-SORT or TrackTrack?

TrackTrack. On the same clip it recorded 4 ID fragmentations against 16, across 14 unique IDs for BoT-SORT and 7 for TrackTrack, with average track lengths of 61.7 and 67.4 frames. ID stability is a property of the algorithm rather than the GPU, so this holds on any hardware.

Is BoT-SORT or TrackTrack cheaper to run?

TrackTrack, at $0.0775 per 1,000 frames on an NVIDIA H100 versus $0.1115. The difference is occupancy: the slower tracker holds the GPU longer per frame, so the cost gap tracks the speed gap.

Can BoT-SORT and TrackTrack run in real time?

BoT-SORT sustained 30 FPS or better on 0 of the 10 GPU tiers and TrackTrack on 0. Per frame on an NVIDIA H100 that is 101.7 ms and 70.6 ms respectively. Anything under 33 ms per frame keeps up with a 30 FPS camera.

Does a more expensive GPU make tracking more accurate?

No. A faster GPU only makes tracking run faster; it does not change how accurately the tracker follows objects. Accuracy and ID-stability depend on the tracking algorithm and your detector, not the hardware. That is why this page reports speed per GPU, but ID-stability only once.

How was this YOLO tracker benchmark run?

Every tracker ran on the same 200-frame clip with the same yolo26n.pt detector, on each of the 10 GPU tiers. FPS is the end-to-end detection-plus-tracking rate. All six trackers are built into Ultralytics, so results are reproducible with a single script.

Tracker comparison · BoT-SORT vs TrackTrack

BoT-SORT vs TrackTrack

A head-to-head of BoT-SORT and TrackTrack for multi-object tracking behind YOLO: how fast each runs across 10 NVIDIA GPUs and how steadily it holds object IDs, measured on the same clip and the same detector.

The verdict: On an NVIDIA H100, TrackTrack is the quicker of the two at 14 FPS versus 10 for BoT-SORT, roughly 1.4× its throughput, and it stays out front on all 10 GPU tiers. TrackTrack is the steadier tracker: 4 ID fragmentations against 16 for BoT-SORT (75% fewer), across 7 unique IDs to 14 on the same clip. That hands TrackTrack both the speed and the cleaner IDs on this hardware, making it the safer default: step up to BoT-SORT for moving-camera footage (drones, dashcams, handheld).

Faster overall

TrackTrack

Higher FPS on 10 of the 10 GPU tiers tested.

Steadier IDs

TrackTrack

Only 4 ID fragmentations, versus 16 for BoT-SORT.

ID-stability: what a fragmentation actually looks like

How well a tracker holds a single, consistent ID on each object is a property of the algorithm, not the GPU, so these numbers barely move across hardware; we report them once (measured on the NVIDIA H100). This clip has no MOT ground truth, so instead of MOTA/IDF1 we report the raw stability signals: how many distinct IDs the tracker created, how many times a track was broken (fragmentations), and the average track length. Fewer IDs and fewer fragmentations mean steadier identities.

Tracker	Approach	Unique IDs	Fragmentations	Avg track length
TrackTrack	Motion + Re-ID	7	4	67.4
BoT-SORT	Motion + camera comp.	14	16	61.7

Speed by GPU

BoT-SORT and TrackTrack, ranked fastest-first. Pick any GPU to see which one leads on that hardware. End-to-end detection + tracking throughput (frames per second, higher is better) for BoT-SORT and TrackTrack across all 10 GPU tiers. GPUs are ordered flagship-first.

Show GPUs

.tabbed-strip { display: none; } .tabbed-panel[hidden] { display: block !important; } .tabbed-panel + .tabbed-panel { border-top: 1px solid var(--color-line); }

BoT-SORT
TrackTrack

Tip: Bold marks the faster tracker on each GPU. Measured with yolo26n.pt on a 200-frame clip.

Tracker	B200	H200	H100	RTX PRO 6000	A100 80GB	A100 40GB	L40S	A10	L4	T4
BoT-SORT	10.5	9.2	9.8	14.7	8.3	8.6	9.3	7.3	9.6	6.3
TrackTrack	14.9	11.1	14.2	21.7	11.3	12.5	13.0	10.5	13.3	9.1

BoT-SORT vs TrackTrack: the four questions that decide it

Every figure below is computed from the same run as the tables above: throughput, per-frame latency, cost and track continuity for this pair specifically, rather than a general ranking.

Real-time headroom

Across the 10 tiers, BoT-SORT clears 30 FPS on 0 and 60 FPS on 0; TrackTrack clears 30 FPS on 0 and 60 FPS on 0. BoT-SORT does not reach 30 FPS on any tier in this run, which puts it in the offline-analysis bracket rather than the live-video one. Per frame on an NVIDIA H100 that is 101.7 ms for BoT-SORT and 70.6 ms for TrackTrack, detection included.

Does the ranking hold across GPUs?

Yes. TrackTrack is ahead of BoT-SORT on all 10 tiers, from the B200 down to the T4, so the ordering you see on an NVIDIA H100 is the ordering you will get on whatever you deploy to. That consistency is itself useful: it means this choice can be made once rather than revisited per hardware refresh.

How long an identity survives

Average track length was 61.7 frames for BoT-SORT and 67.4 for TrackTrack on the 200-frame clip, so TrackTrack held each object for longer before losing or re-numbering it. Read alongside the fragmentation counts, that is what an ID switch feels like downstream: a counting line double-counts the same person, or a dwell-time average collapses because one visit was recorded as three. Neither number is MOTA, because this clip has no ground truth, but both come from the same run and point the same way.

Cost to run

At NVIDIA H100 rates, TrackTrack costs $0.0775 per 1,000 frames against $0.1115 for BoT-SORT, about 1.4× cheaper. Over a single 30 FPS camera running for an hour that is roughly $8.37 versus $12.05. That is small per camera, and a real multiplier across a wall of them. Cost here is pure occupancy: a slower tracker holds the GPU for longer, so throughput and spend are the same fact in two units.

Choosing between them

Choose BoT-SORT if…

Moving-camera footage (drones, dashcams, handheld).

Strengths

Handles camera motion well
Stable IDs with Re-ID enabled
Ultralytics' default tracker

Trade-offs

Slowest here with Re-ID + GMC on
Heavier to run in real time

Motion + camera comp., 2022. Enable it with tracker="botsort.yaml".

Choose TrackTrack if…

Offline / batch analysis where ID correctness is paramount.

Strengths

Fewest fragmentations of any tracker
Most consistent identities
State-of-the-art association

Trade-offs

Much slower, not for real time
Heaviest tracker to run

Motion + Re-ID, 2025. Enable it with tracker="tracktrack.yaml".

Other head-to-head comparisons

More matchups involving BoT-SORT and TrackTrack, each with the same speed, cost and ID-stability breakdown.

See the full 6-tracker benchmark across 10 GPUs →

How these numbers were measured

BoT-SORT and TrackTrack ran on the identical 200-frame clip with the same yolo26n.pt detector on each of the 10 GPU tiers, so the only variable is the tracker. There is no MOT ground truth on this clip, so no MOTA or IDF1 is claimed; the stability figures are raw counts. Full methodology and the benchmark script live on the hub, alongside all six trackers.

Blog

From the blog

Tutorials, code, and notes on computer vision, deep learning, and applied AI.

View all posts →

Frequently asked questions

Is BoT-SORT faster than TrackTrack?: On an NVIDIA H100 with yolo26n.pt, BoT-SORT ran at 10 FPS and TrackTrack at 14 FPS end to end, detection included. Across all 10 GPU tiers BoT-SORT was ahead on 0 and TrackTrack on 10. The ordering is the same on every tier tested.
Which holds object IDs better, BoT-SORT or TrackTrack?: TrackTrack. On the same clip it recorded 4 ID fragmentations against 16, across 14 unique IDs for BoT-SORT and 7 for TrackTrack, with average track lengths of 61.7 and 67.4 frames. ID stability is a property of the algorithm rather than the GPU, so this holds on any hardware.
Is BoT-SORT or TrackTrack cheaper to run?: TrackTrack, at $0.0775 per 1,000 frames on an NVIDIA H100 versus $0.1115. The difference is occupancy: the slower tracker holds the GPU longer per frame, so the cost gap tracks the speed gap.
Can BoT-SORT and TrackTrack run in real time?: BoT-SORT sustained 30 FPS or better on 0 of the 10 GPU tiers and TrackTrack on 0. Per frame on an NVIDIA H100 that is 101.7 ms and 70.6 ms respectively. Anything under 33 ms per frame keeps up with a 30 FPS camera.
Should I choose BoT-SORT or TrackTrack?: Choose BoT-SORT for moving-camera footage (drones, dashcams, handheld). Choose TrackTrack for offline / batch analysis where ID correctness is paramount. Camera-motion compensation for moving cameras. Research-grade stability, the fewest ID breaks of all.
Does a more expensive GPU make tracking more accurate?: No. A faster GPU only makes tracking run faster; it does not change how accurately the tracker follows objects. Accuracy and ID-stability depend on the tracking algorithm and your detector, not the hardware. That is why this page reports speed per GPU, but ID-stability only once.
How was this YOLO tracker benchmark run?: Every tracker ran on the same 200-frame clip with the same yolo26n.pt detector, on each of the 10 GPU tiers. FPS is the end-to-end detection-plus-tracking rate. All six trackers are built into Ultralytics, so results are reproducible with a single script.