4 ms·
We also do about 12M API requests per day: http://duckduckgo.com/traffic.html http://duckduckgo.com/traffic.html
by yegg 14y ago
We also do about 12M API requests per day: http://duckduckgo.com/traffic.html http://duckduckgo.com/traffic.html
- ithkuil 14y agoThe interesting measure is what is the peak rps EDIT: I mean, it ~150 doesn't seem that much, but I'm sure the requests are not uniformly distributed, so the system should be able to handle much more than that within reasonable latency bounds.
- 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.
- druiid 14y agoIndeed. Peak RPS is what is going to be interesting. Depending on where traffic is from, it's very possible to have 12 mil requests in a day only from 9-5 type of hours and a big huge empty space during the night (This is the kind of traffic my company sees).
- johansch 14y agoInteresting. Any public big users of the API?
- yegg 14y agoFastestFox is the biggest.
- rehack 14y agoGreat article. Thanks. Could you please share, the good things you did which made the direct searches jump during Jan-2012 to Mar-2012?