-
Type: Task
-
Resolution: Unresolved
-
Priority: Minor - P4
-
None
-
Component/s: Performance Benchmarking
-
None
-
Needed
In addition to timing data, all micro-benchmark tasks will be measured in terms of "megabytes/second" (MB/s) of documents processed, with higher scores being better. (In this document, "megabyte" refers to the SI decimal unit, i.e. 1,000,000 bytes.) This makes cross-benchmark comparisons easier.
However, each driver's benchmark suite reports different measurements right now. Python reports "bytes_per_second", Java reports ops_per_second, C says "ops_per_second" but actually reports bytes/sec, etc..
We should also standardize the "Test" names that are reported so that we can more easier compare results across drivers. For example, the "GridFS download" test is called "GridFS Download" in Java, "TestGridFsDownload" in Python and C, "gridFsDownload" in Node.
Related to DRIVERS-2666.
- is related to
-
NODE-5794 Upload test results for individual perf tests in addition to composite scores
- Closed
- related to
-
PYTHON-3823 Standardize performance testing infrastructure
- Closed
-
DRIVERS-2666 Standardize performance testing infrastructure
- Implementing