You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There has been variable latency observed when using the last cache under higher concurrent query loads. There are no tracing spans to indicate where in the scan time is being taken, and contributing to that latency, in the last cache.
Proposed solution
Extract the span context from the DataFusion Session that is provided to the TableProvider::scan implementation for the last_cache:
Problem statement
There has been variable latency observed when using the last cache under higher concurrent query loads. There are no tracing spans to indicate where in the scan time is being taken, and contributing to that latency, in the last cache.
Proposed solution
Extract the span context from the DataFusion
Session
that is provided to theTableProvider::scan
implementation for thelast_cache
:influxdb/influxdb3_cache/src/last_cache/table_function.rs
Lines 71 to 77 in d8efdb4
It would be worth wrapping a span around the following to generate traces:
influxdb/influxdb3_cache/src/last_cache/table_function.rs
Lines 84 to 89 in d8efdb4
influxdb/influxdb3_cache/src/last_cache/table_function.rs
Line 90 in d8efdb4
Within the latter, we could break down into more spans:
influxdb/influxdb3_cache/src/last_cache/cache.rs
Lines 427 to 458 in d8efdb4
influxdb/influxdb3_cache/src/last_cache/cache.rs
Lines 460 to 463 in d8efdb4
Additional context
This is related to #25562
The text was updated successfully, but these errors were encountered: