-
Type: Sub-task
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
The first part of performance hits during logging actually occurs during the command monitoring stage, even with logging disabled. Here's an example with no command monitoring and command monitoring:
largeDocBulkInsert | megabytes_per_second | n/a | 31.0216885085 | 11.7661826882 |
largeDocInsertOne | megabytes_per_second | n/a | 44.369467752 | 14.4284864574 |
First step to improve logging will be to improve this first step, most notably around the command deep copy.