Use Case

As a Node engineer
I want CSOT performance to be optimal
So that it comes at a low cost to enable for existing workflows

User Experience

• What is the desired/expected outcome for the user once this ticket is implemented?
  • More performant timeout value calculation
• If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?
  • Not a bug

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 related to CSOT or socket timeouts
• 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?
  • Yes

Acceptance Criteria

Implementation Requirements

• Reduce duplication of socket timeout code

Testing Requirements

• Ensure the same timeouts are being set before and after this change with CSOT enabled/disabled

Documentation Requirements

• None

Follow Up Requirements

• Investigate more performance improvements to CSOT
• 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