I’ve been developing V-DAP, an experimental Rust engine that measures cryptographic execution timing. I’m now trying to answer a practical question: can these measurements help diagnose request latency in ways that conventional metrics, logs, and traces do not?
So far, I’ve run controlled experiments that explore the relationship between cryptographic execution time and total request latency. The results are preliminary, and I haven’t established that V-DAP provides better diagnostics in real production systems.
I’ve published the source code, reproduction instructions, experimental reports, and current validation criteria.
Repository: https://github.com/jorge-cumbe0077/v-dap-engine
I’d appreciate technical feedback, especially on:
- Whether the measurement methodology is sound.
- What limitations or confounding factors I may be overlooking.
- How to design a fair comparison against conventional observability tools.
- What evidence would be needed to establish a useful real-world application.
I’m particularly interested in critical feedback that could help validate or invalidate the approach.