Optimize how we track data for persistence
#89370Comparing
optimized_change_tracking
(b3d4105
) withcanary
(a5f6590
)+4%
- Improvement
- 1
- Untouched
- 16
- Skipped
- 3
Benchmarks
3 total
The benchmarks below were skipped, so their baseline results are used instead. If they were deleted in your codebase, archive them to remove them from the performance reports.
Learn more about archiving benchmarks
Learn more about archiving benchmarks
hmr_updates_medium_10
crates/next-api/benches/hmr.rsIgnoredSkipped
17.2 µs*
hmr_updates_large_20
crates/next-api/benches/hmr.rsIgnoredSkipped
16.9 µs*
hmr_updates_small_5
crates/next-api/benches/hmr.rsIgnoredSkipped
16.8 µs*
Commits
Click on a commit to change the comparison rangeBase
canary
a5f6590
+3.68%
Optimize how we track data for persistence
eb9af29
17 hours ago
by lukesandberg+0.03%
fix clippy issue
91e1a12
17 hours ago
by lukesandberg+0.17%
fix some documentation and parallise end_snapshot
87071fe
17 hours ago
by lukesandberg-0.23%
simplify callbacks
b3d4105
4 hours ago
by lukesandberg