[SERVER-56454] Don't record read operations in resmoke's configuration tracker Created: 29/Apr/21 Updated: 29/Oct/23 Resolved: 30/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Siran Wang (Inactive) | Assignee: | Siran Wang (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | Linux | ||||
| Sprint: | STM 2021-05-03, STM 2021-05-17 | ||||
| Participants: | |||||
| Linked BF Score: | 151 | ||||
| Story Points: | 1 | ||||
| Description |
|
Resmoke.py records the call stack of all read and write operations to detect potential conflicts. The read operations are numerous and consumes a high amount of memory, especially on the ASAN build variant. We therefore disable tracking of read operations to reduce resmoke's memory consumption |
| Comments |
| Comment by Githook User [ 30/Apr/21 ] |
|
Author: {'name': 'Siran Wang', 'email': 'siran.wang@mongodb.com', 'username': 'vincivans'}Message: |
| Comment by Robert Guo (Inactive) [ 29/Apr/21 ] |
|
acm The ticket description has been updated. PTAL. (It's a change in resmoke) |