[SERVER-32730] WiredTiger read-write performance for the insert benchmark Created: 17/Jan/18 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Mark Callaghan | Assignee: | Backlog - Performance Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Product Performance
|
||||
| Participants: | |||||
| Description |
|
This covers read-write performance for the insert benchmark. Other issues are open for load performance (SERVER-32707) and full scan performance (SERVER-32711). I will start with results from inMemory-16 (database in memory, 16 clients, 16 collections) and the test where each writer is limited to 100 inserts/second, there are 16 collections, 16 query clients and 16 writer clients with a query/writer pair per collection. The first table has throughput and HW efficiency metrics:
From these results:
The worst case response times are:
|
| Comments |
| Comment by Ramon Fernandez Marina [ 18/Jan/18 ] | ||||||||||
|
Thanks for the detailed information mdcallag, adding to the backlog for investigation. | ||||||||||
| Comment by Mark Callaghan [ 17/Jan/18 ] | ||||||||||
|
And for ioBound-none (16 clients, 16 collections, no compression, database larger than RAM) The metrics are:
Summary:
Worst-case response time:
I haven't provided it for previous tests but my insert benchmark client maintains response time histograms. There are per client, so there are 16 histograms in the test with 16 clients. For this test, this is one of the histograms for WiredTiger and then InnoDB
| ||||||||||
| Comment by Mark Callaghan [ 17/Jan/18 ] | ||||||||||
|
And now for inMemory-1 (16 clients, 1 collection, in-memory database) the results with each writer limited to 1000/second. Summary:
Worst case response times:
| ||||||||||
| Comment by Mark Callaghan [ 17/Jan/18 ] | ||||||||||
|
Still using inMemory-16, results for the test with each writer limited to 1000 inserts/second. Summary:
Worst case response times:
|