[SERVER-75868] Performance experiment: Hide the cost of makeOperationContext() "behind" the cost of sourcing the work item Created: 07/Apr/23  Updated: 18/Apr/23  Resolved: 18/Apr/23

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

Type: Engineering Test Priority: Major - P3
Reporter: Vojislav Stojkovic Assignee: Alex Li
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: HTML File SERVER-75868-diff     File SERVER-75868.csv    
Sprint: Service Arch 2023-04-17, Service Arch 2023-05-01
Participants:

 Description   

Similar to what we did in v4.4 by moving the destruction of the operation context after we've sunk the response over the network, we would like to try moving the creation of the operation context to the point where we're starting the session workflow iteration, before sourcing the request. The idea is that the client will take some time to prepare the request before sending it, and we could pay the cost of operation context creation during that time.

The goal of this ticket is to do preliminary performance testing to check whether moving the creation of operation context to the beginning of the session workflow iteration would yield any performance improvements.


Generated at Thu Feb 08 06:31:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.