GoogleCloudPlatform / GoogleCloudPlatform/PerfKitBenchmarker
If we patch UnixBench - should we continue to call it UnixBench?
Open
question
- Dominant language
- Python
- Stars
- 2k
- Forks
- 562
- Avg merge
- 4h 55m
- Merged PRs (30d)
- 69
Description
I believe we should patch it to run on 16+ cores, this is not what this issue is about. Also we should probably patch it on UnixBench's own depo, also not what this issue is about.
The question here is that, assuming we do patch it (or any other benchmark), shall we continue to call it UnixBench? Or should we call it UnixBench++ or similar?
My proposal is to name it UnixBench.[patch_name] or UnixBench.patch_revision.
Contributor guide
Assessment
This issue has not been assessed yet.