-
Notifications
You must be signed in to change notification settings - Fork 13.3k
WIP (do not merge): Performance test for zlib-ng-compat #75732
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
@bors try @rust-timer queue |
Awaiting bors try build completion |
⌛ Trying commit 08e06af56c96cb72fc04627437c6a278396c8a74 with merge 86b2c01be5672069ae4742dc7330133e9acb017c... |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
💔 Test failed - checks-actions |
08e06af
to
b86161b
Compare
@bors try @rust-timer queue |
Awaiting bors try build completion |
⌛ Trying commit b86161b1e88045064177caeeb71cb1117a329517 with merge 0991e982415f7bc29d102f3268e50132d3367d84... |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
💔 Test failed - checks-actions |
b86161b
to
b8e3e0b
Compare
Evidently zlib-ng requires a newer cmake than the one from the version of mingw we're using. This experiment will need to wait until we update mingw cmake. |
MinGW does not provide CMake. The builder used CMake 3.10.2 because that's what Ubuntu 18.04 provides as |
@joshtriplett I've reported that build error to the upstream: zlib-ng/zlib-ng#729 |
@mati865 Thanks! Worth a try, then. |
@bors try @rust-timer queue |
⌛ Trying commit b8e3e0b with merge 69677eb315b30092708001efd2ee7aa01465e749... |
Awaiting bors try build completion |
⌛ Trying commit b8e3e0b with merge 101b1b679086e6a473cf43f6b3876b2376bc83f9... |
Your PR failed (pretty log, raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
☀️ Try build successful - checks-actions, checks-azure |
Queued 101b1b679086e6a473cf43f6b3876b2376bc83f9 with parent 5fff382, future comparison URL. |
Looking at the binaries, it looks like they're still getting linked to system libz through LLVM, so this may not give accurate results. |
Finished benchmarking try commit (101b1b679086e6a473cf43f6b3876b2376bc83f9): comparison url. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up. @bors rollup=never |
Not bad! Zero regressions, tiny improvements across the board, a few larger improvements. We'd likely get even more improvement by switching to an even faster compression format, like lz4 or snappy. But this test shows that there's performance to be gained. |
Test PR for a perf run with zlib-ng-compat. rustc uses flate2 to
compress and decompress metadata (and in some cases LLVM bytecode), and
it's worth evaluating the potential performance improvement here. This
would require more care (and a config.toml setting) to do properly.