-
Type: Sub-task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
Use Case
As a Node.js engineer
I want to improve the performance of the driver
So that it can be super fast
User Experience
- What is the desired/expected outcome for the user once this ticket is implemented?
- The Node driver does not regress in performance because of the introduction of the CSOT feature
- If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?
Dependencies
- upstream and/or downstream requirements and timelines to bear in mind
- CSOT
Risks/Unknowns
- What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
- Introduce bugs unforeseen by testing
- Is there an opportunity for better cross-driver alignment or testing in this area?
- No
- Is there an opportunity to improve existing documentation on this subject?
- No
Acceptance Criteria
Implementation Requirements
- Inline Uint8Array declaration in ServerSession clone
- Remove defineProperty call in endSessions
Testing Requirements
- Ensure all tests pass and the code paths changed are covered
- Check benchmarks for improvements
Documentation Requirements
- None
Follow Up Requirements
- additional tickets to file, required releases, etc
- None
- if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward
- N/A
- is related to
-
NODE-6531 Perf: Cache namespace parsing logic
- Backlog