3 ms·
Maybe? As an experienced engineer, you should be able to use your experience to estimate the latency. Very few things are truly novel.
by sumy23 4y ago
Maybe? As an experienced engineer, you should be able to use your experience to estimate the latency. Very few things are truly novel.
- _gabe_ 4y agoAs an experienced engineer, you should know that you can never give a good estimate. Very few things are as you would expect them to be. I looked for an article on how to estimate latency. When I Google "how to estimate the latency of my program" the top results are: "Network Latency Guide: How to Check, Test, & Reduce" "How to Measure Latency - Obkio" "How to measure network latency: the 5 best tools - Kadiska" They're all about measuring latency. Honestly I can't find any blog or guide that talks about how to give good estimates. Every time I Google a different variation of this question, it only gives me results that talk about how to measure latency. If you can point me to a good source that talks about how you can provide a good estimate of latency, I would be very surprised ;)
- pclmulqdq 4y agoUse a table of common latencies, add up what's going to happen on your critical path, and multiply by 2. That will be close to your median latency. Edit - when people ask for estimates, they usually aren't asking if it's 1 millisecond or 2 milliseconds. They're asking if it's closer to 1 millisecond or 100 milliseconds.