-
Type: Task
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
Spreadsheet: Large BSON Serialization causes degradation
Use Case
As a.. Node Driver user
I want... Logging to not slow down my application by 100x in certain cases
So that... My application is efficient even when logging is turned on.
Unknowns
If the problem is converting BSON to JSON that will end up being truncated, is this something that On-Demand BSON could help with? E.g. implementing a reviver that only generates a string up to the point it would have been truncated.
Acceptance Criteria
Implementation Requirements
- Do not serialize entire BSON document if it is large than truncation length
- Can maybe follow Java Driver's implementation here.
- Add newline to log lines
- See tech chat discussion summary here
Testing Requirements
- Run perf on logging worst case and ensure all test cases are <1.2x as slow as base
- Cases:
- Worst case: trace on everything
- Support case: debug (same as trace since we don't have trace logs)
- Production use case: error or warn level logs (we don't have any of these logs right now, but we can run the setting just as a sanity check)
- is related to
-
NODE-5837 Standardized logging with large documents causes a large performance drop
- Closed
1.
|
Improve Performance of Command Monitoring | NODE-6452 | In Progress | Durran Jordan |