Details

We have an impacted SingleStore (MemSQL) Integrate channel experiencing high latency and I/O delays. We need the ability to capture detailed performance information at the channel/job level to identify where the delay is occurring.

Currently:

• HVR_TIME_PROFILER_TRACE is not supported for MySQL/MemSQL (SingleStore).
• HVR Support confirmed this is a product limitation, not a configuration issue.
• We tried:
  • HVR_TIME_PROFILER_TRACE=LOW
  • HVR_PERFORMANCE_METRIC_ENABLE=1
  • HVR_SQL_TRACE=1
• HVR_SQL_TRACE can provide SQL/per-statement duration information, but it does not provide the required CPU and I/O performance details.
• HVR_TIME_PROFILER_TRACE provides useful timing information such as Functional Calls, Network I/O and SQL timing, but this functionality is currently unavailable for SingleStore/MemSQL.

Feature Request:

Please consider adding support for HVR_TIME_PROFILER_TRACE for SingleStore/MemSQL Integrate channels, including:

• CPU utilization/time
• Network I/O
• Database I/O
• SQL execution time
• Functional/call timing
• Overall source/hub/target timing breakdown

Ideally, this should be configurable at the channel/job level, so performance data can be captured for a specific impacted channel without enabling extensive tracing across the entire HVR Hub.

This capability would help us troubleshoot SingleStore Integrate channel latency and identify whether the bottleneck is related to HVR processing, network I/O, SQL execution, or the target database.

Expected outcome:
Ability to enable detailed performance profiling for SingleStore/MemSQL Integrate channels similar to the profiling available for supported target technologies.