Revert to using Ubuntu 18.04 for the wrk image #7832
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There has been a significant performance regression after #7783 (e.g. check the composite scores), and this PR is an attempt to figure out where the issue is.
In addition to the
wrkversion update, PR #7783 made the following the changes:wrk- I checked the raw data for theh2oimplementation (which covers all defined tests and has been affected negatively) and there were no differences in the valueswrk- the new ones do not have any effect in the continuous benchmarking environment (unlike on other platforms)Concerning the last point, it is possible that the system libraries (e.g. the memory allocator) have received additional security hardening compared to 18.04, which causes the slowdown, so this PR tries to check this theory. Since 18.04 will stop being supported in less than half a year and given that this project is meant to represent a realistic production environment, I expect that we will return to 22.04 eventually, but in the meantime it does not hurt to be aware of any costs.