Simple nightly benchmark #235
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.
What was changed
Create simple/naive nightly benchmark that uses fibers. This is mostly a sanity test that Ruby performs well with some load, we just happen to run it nightly. No big surprises here. We use the same methodology as Python and .NET nightlies. For example, here is the 10000 workflow bench on the latest Ruby run compared to the last night's Python run and .NET run:
Ruby:
Python:
.NET:
Can see Ruby is probably a tad-yet-negligibly faster than Python, which is to be expected given the Python sandbox, and both are slower than .NET which is obviously expected. Python has a lot less higher max mem because its GC runs way more frequently than Ruby and .NET (not even sure Ruby's runs at all in this test, but I will confirm there are no mem leaks). Lots of these numbers are variable because they are probably pushing the CLI dev server too hard (lots of RPS warn limit logs). And obviously there is no tuning done on the weak 4 core GH worker or the worker options to get the most, so don't read these as "proper workflow/sec numbers" by any means.
Checklist