[SERVER-58414] Evaluate the performance of the new workload on master Created: 12/Jul/21  Updated: 29/Jul/21  Resolved: 29/Jul/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Antonio Fuschetto
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-58413 Create/Find a workload that does CRUD... Closed
Related
is related to SERVER-58415 Evaluate the performance of the new w... Closed
Sprint: Sharding 2021-07-12, Sharding EMEA 2021-07-26, Sharding EMEA 2021-08-09
Participants:

 Description   

The goal of this task is to evaluate the performance of the new workload introduced on SERVER-58413 on master.



 Comments   
Comment by Antonio Fuschetto [ 27/Jul/21 ]

The script, testing the performance of the business cases described on SERVER-58413, has been run on both the master version and after SERVER-58416.

The complete test results are available at Workloads: Move chunk with load, and the Comparison tab highlights the differences in terms of performance between the two samples.

The performance metrics measured by the script are:

  • Read ops throughput before moveChunk (op/sec)
  • Read ops throughput during moveChunk (op/sec)
  • Write ops throughput before moveChunk (op/sec)
  • Write ops throughput during moveChunk (op/sec)
  • MoveChunk ops throughput (doc/sec)
  • Commit critical section duration (msec)
  • Total critical section duration (msec)

In a nutshell, this test highlights that SERVER-58416 increased the execution time of the commit critical section of the moveChunk command of about 50%. This value appears to be in line with our forecasts.

Generated at Thu Feb 08 05:44:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.