[SERVER-61808] The cloning of sessions of the moveChunk gets slower after some migrations Created: 30/Nov/21 Updated: 22/Dec/21 Resolved: 22/Dec/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 5.1.0 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | Luis Osta (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | sharding-nyc-subteam1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Sharding 2021-12-13, Sharding 2021-12-27 | ||||||||
| Participants: | |||||||||
| Description |
|
As part of PM-2423 we have been measuring the performance of the migration protocol. We saw some weird numbers related to the cloning of the sessions that would be interesting to understand. Environment Experiment After that we execute a few thousand random migrations. There are not CRUD operations during the execution of this phase. You can check the Genny worload we executed here. Results We are plotting two different variables:
The interesting time is the first one, the second one is more or less constant. We can see an slow down of 30x between the first move chunks and the lasts ones on my machine, after 4K moveChunks. We also got some numbers on EVG, you see them on the different tabs. |
| Comments |
| Comment by Luis Osta (Inactive) [ 22/Dec/21 ] |
|
I've filed |