|
|
|
|
|
by tahoecoder
4793 days ago
|
|
Creating a daily average of concurrent visits isn't relevant. Servers don't take an average of all the possible future hours of complete inactivity when they are serving up requests. The post was only up at the top for a couple of hours before the server performance got so bad such that everyone started flagging it. My post then dropped off the front page and quickly went to page 4 or 5 due to the flagging. I agree with you that the more interesting number would be the the concurrent number of requests. |
|
I did that math to demonstrate that you are misunderstanding the relevancy of the Chartbeat number: that yes, if you look at the values "over 45 minutes" that is slightly weird, but entirely accurate, as it is not in any way unlikely that you had a spike four times your average during the day (that's why I had to calculate the average: to see if your maximum value was unexpected; I did the calculation of the average using the way of interpreting the chart which you believe is flawed, and it turns out that it is entirely consistent).
> The post was only up at the top for a couple of hours before the server performance got so bad such that everyone started flagging it.
Sure: your site was slow (I'm not questioning that your site was slow: tons of websites hit HN and then fall apart, it seems to be a daily occurrence), but I still don't know how you accomplished it with this small a number of users.