Can cryptographic execution timing add useful information to latency…

I'm developing V-DAP, an experimental Rust engine that measures cryptographic execution timing. I'm trying to determine whether those measurements provide useful diagnostic information beyond conventional observability tools.

The practical problem I'm investigating is this: when a service experiences latency spikes, can measurements of cryptographic execution help distinguish between possible sources of delay, or do standard metrics, tracing and profiling already provide the same information?

My current experiments are preliminary. In a controlled HTTP pilot, I observed a strong correlation between the measured cryptographic interval and total request latency. In a separate experiment, I introduced a deliberate delay outside that interval and observed the request latency increase. These results demonstrate temporal decomposition in those test conditions, not scheduler causality or a proven diagnostic advantage.

What I want to validate next:

Can V-DAP help distinguish two known causes of latency?
Does it improve diagnostic accuracy or time-to-diagnosis compared with conventional tools alone?
What confounders and measurement overhead should I investigate?
What experiment would convince you that this has practical engineering value?

Repository and reproducibility details:
https://github.com/jorgecumbe0077/v-dap-engine

I'm looking for critical technical feedback, including reasons this approach may not be useful. I don't claim that V-DAP is production-ready or that it prevents timeouts.

Impact

Currently, there is no demonstrated security impact or vulnerability. The project focuses on latency diagnosis and observability rather than exposing or exploiting security flaws. It does not claim to prevent timeouts or improve security posture. No active exploits or vulnerabilities are associated with this tool.

Defensive guidance

No mitigation is required as this is an experimental research project without identified security vulnerabilities or threats. The tool is not production-ready and does not pose a security risk. Users should treat it as a research prototype and not rely on it for operational security or latency diagnostics.

Summary

V-DAP is an experimental tool that measures the timing variability of cryptographic operations to investigate if this data can aid in diagnosing latency spikes in services. Initial controlled experiments demonstrated a correlation between cryptographic execution time and overall request latency, and the ability to detect introduced delays outside the cryptographic interval. However, these results do not establish causality or guarantee improved diagnostics over standard metrics, tracing, and profiling. The project is in early research stages, not production-ready, and does not claim to prevent timeouts or improve service-level objectives. The repository includes source code, experimental reports, and instructions for reproducibility, emphasizing the exploratory nature and limitations of the findings.

Can cryptographic execution timing add useful information to latency diagnosis?

Discussion

Links cited in the discussion

Impact

Defensive guidance

Summary

References

Community reviews

Discussion

Links cited in the discussion

AI analysisMachine-generated, updated 26 Oct 2026, 12:22 UTC

Technical details

References

Community reviews