[IGNITE-13411] Optimize tracing when NoopTracingSpi is used

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9
• Fix Version/s: 2.9
• Assignee: Aleksey Plekhanov
• Reporter: Aleksey Plekhanov
• Created: 07/Sep/20 15:17
• Updated: 05/Aug/21 11:48
• Resolved: 10/Sep/20 09:34

Description

Current tracing implementation has some redundant actions for no-op tracing SPI which have a negative impact on performance:

1. GridNioTracerFilter added to communication SPI filters chain even if tracing is disabled.
2. MTC.support/MTC.supportContinual methods in case of no-op span or null span return TracingSurrounding which equivalently does nothing (span.set(oldSpan) is redundant, since span.set(startSpan) was skipped for no-op or null span, and endRequired is always false. So, instead of creating new TracingSurrounding we can return null (correctly processed by try-with resource block) with the same effect and get rid of some code on the hot path.
3. Sometimes we already have Span on hands and call to MTC.span() is redundant.

Issue Links

• links to: GitHub Pull Request #8223
• links to: GitHub Pull Request #8224