3 ms·
from what I can tell by observing HN the server goes down several times an hour and has a script wrapped around it to keep it up Very interesting. That sounds
by riffer 17y ago
from what I can tell by observing HN the server goes down several times an hour and has a script wrapped around it to keep it up
Very interesting. That sounds a little like an equivalent of MaxRequestsPerChild, which makes sense given it's a custom webserver, rather than Apache. How do you synch up what you're seeing with this:
http://news.ycombinator.com/item?id=1048348 http://news.ycombinator.com/item?id=1048348
Why doesn't the leaderboard do this a couple of times an hour?
- jacquesm 17y agoThat's a good question, I don't know. The symptom is invariably the same, the connection is refused for a bit and then the server is back up again as if nothing happened. The times that it is down vary from just a few seconds to 10's of seconds, but rarely more than that. It would be nice to know what is going on there, it certainly doesn't look very good. Also HN can be terribly slow at times, much slower than would make sense given the number of people visiting it on a daily basis. To see if that bug still exists I just tried it by requesting vaksels posting history and sure enough the connection timed out and the server was unreachable for a short while, then came back up. http://news.ycombinator.com/submitted?id=vaksel http://news.ycombinator.com/submitted?id=vaksel Does it work for you? It's a pretty weird bug.
- riffer 17y agoI agree on the general speed. The server is one process / single thread, and since on the speed spectrum arc is all about exploratory programming and not benchmarking speed ... I've also noticed that connections get dropped a lot here. Usually it seems to be when I've loaded several pages in quick succession, and so I'd taken it to be anti-scraping IP throttling. I guess one could try to reach it through a proxy right after an event. Also, that particular link works for me now. IIRC, the lazy loading is item-based so there may be some element of prioritizing connections based on whether or not the items requested are in memory. That would also be consistent with an anti-scraping approach. Of course this is all wild speculation on my part.