4 ms·
> within reasonable latency bounds Have you used DDG? Requests take over 500-600ms regularly for me. Compare to Google's instant search and excellent latency f
by badgar 14y ago
> within reasonable latency bounds
Have you used DDG? Requests take over 500-600ms regularly for me. Compare to Google's instant search and excellent latency for non-instant queries... which handle orders of magnitude more traffic.
- ithkuil 14y agoI'm not a DDG user, but it's easy to measure: $ time I=$((I+1)) curl -s "https://duckduckgo.com/d.js?q=test&t=A&l=us-en&p=1&s=0" >/dev/null I=$((I+1)) curl -s "https://duckduckgo.com/d.js?q=test$i&t=A&l=us-en&p=1&s=0" 0.01s user 0.00s system 3% cpu 0.256 total I saw it go over 800ms a couple of times, anyway, I don't intend to run a DDG benchmark. However, just for the sake of the discussion, about architecture and language choice etc, the interesting part would be to see how many rps before starting to degrade. There is no point bashing it and comparing it to other search engines that have more resources behind them.