Comparing
fix-benchmark-coverage
(216ac1e
) withmain
(03df045
)0%
- Untouched
- 5
- Archived
- 1
Benchmarks
6 total
test_multipart_simple_form
tests/test_benchmarks.py+1%
109.3 µs108.1 µs
test_multipart_worstcase_boundary_chars
tests/test_benchmarks.py0%
206.3 µs205.3 µs
test_multipart_large_form
tests/test_benchmarks.py0%
92.3 µs92 µs
test_multipart_file_upload
tests/test_benchmarks.py0%
1 ms1 ms
test_querystring_large_form
tests/test_benchmarks.py0%
1.2 ms1.2 ms
The benchmarks below were run, but are now archived.
If they were deleted in another branch, consider rebasing to remove them from the report.
If they were added back in this branch, you can restore them to include them in future performance reports.
Learn more about archiving benchmarks
If they were deleted in another branch, consider rebasing to remove them from the report.
If they were added back in this branch, you can restore them to include them in future performance reports.
Learn more about archiving benchmarks
test_multipart_long_boundary
tests/test_benchmarks.pyArchived
N/A
N/A995.6 µs
Commits
Click on a commit to change the comparison rangeBase
main
03df045
+0.57%
Make benchmark coverage trigger the partial-boundary fallback
bf8ea52
16 hours ago
by Kludex-0.18%
Use CRLF for worstcase_bchar body to match internal boundary prefix
216ac1e
16 hours ago
by Kludex