4 ms·
I don't think I have enough context to understand this article. What exactly does "response time" measure, here? The diagram of the system makes it look like t
by gue5t 10y ago
I don't think I have enough context to understand this article.
What exactly does "response time" measure, here? The diagram of the system makes it look like this program is essentially just a scan over a data stream, so each iteration should be minimally computationally intensive--certainly not in the tens of milliseconds.
Is this counting time to query the left-hand-side? Or is it time from receiving a message from the LHS to forwarding it rightward?
I don't know what a "HTTP log drain front-end" is: is this software an HTTP client, or an HTTP server? If making HTTP requests across some network is costing you up to 10ms, what network is that, and why not simply run this code on the host that generates the data you're currently sending over HTTP?
- ukyrgf 10y agoI got an eery vibe that this was the equivalent of an /r/SubredditSimulator post for Hacker News.
- throwanem 10y ago"Log drain" appears to be a Heroku term of art for something that can receive shipped log data from their infrastructure, so an "HTTP log drain front-end" would be a client; if that or something like it is in play here, it would explain why they don't host the aggregator in the same place as whatever's generating the log entries it ingests. 40 requests/second does sound somewhat low, but that may just be the average rate at which whatever they're aggregating generates log entries, rather than a limit enforced by resource exhaustion.