3 ms·

Or use the Coral CDN by appending nyud.net to the host: http://rohanprabhu.com.nyud.net/?p=161 http://rohanprabhu.com.nyud.net/?p=161 It preserves images bett

by mkenyon 16y ago

Or use the Coral CDN by appending nyud.net to the host: http://rohanprabhu.com.nyud.net/?p=161 http://rohanprabhu.com.nyud.net/?p=161 It preserves images better than ViewText does.

ronnier 16y ago
I only cache the HTML, not images. I just don't have enough money for hosting :-p
deno 16y ago
All I get are 408 Time-outs now. As I've mentioned before[1] CoralCDN isn't very good at preserving content that is already down. If OP knew his hosting wasn't very well suited for handling load spikes HN users can generate, he should have posted the original link behind the cdn. At this point the only thing OP could do is to create a rule to redirect to .nyud.net link if the referrer equals HN. [1] http://news.ycombinator.com/item?id=2235559 http://news.ycombinator.com/item?id=2235559
- dspillett 16y ago
  At this point the only thing OP could do is to create a rule to redirect to .nyud.net link if the referrer equals HN. At this point there might be nothing the OP can do except wait until the initial hump of traffic has died down: ifthe server really is completely bogged down he may not even be able to open SSH session to make any config changes. For an article like this, that does not need any dynamic content, would be better served by an event based server as these tend to cope better on low-end boxes in the presence high demand for static content than thread or process based servers. Or, like you say, stick with the current web server setup and post links to high volume sites via a cache like CoralCDN.
  - deno 16y ago
    > At this point there might be nothing the OP can do except wait until the initial hump of traffic has died down: ifthe server really is completely bogged down he may not even be able to open SSH session to make any config changes. I actually did some testing at that moment, before I edited the part you have quoted (I added this later), and I'm confident OP could have probably rescued it if he wanted to. But I agree, it's pretty much game over because you can't edit the link after you've submitted it. So if you're not prepared to handle dense traffic, it's a good idea to submit coralled link instead or put your website behind CloudFront temporarily.

by mkenyon 16y ago

Or use the Coral CDN by appending nyud.net to the host: http://rohanprabhu.com.nyud.net/?p=161 http://rohanprabhu.com.nyud.net/?p=161 It preserves images better than ViewText does.

ronnier 16y ago

I only cache the HTML, not images. I just don't have enough money for hosting :-p

deno 16y ago

All I get are 408 Time-outs now. As I've mentioned before[1] CoralCDN isn't very good at preserving content that is already down. If OP knew his hosting wasn't very well suited for handling load spikes HN users can generate, he should have posted the original link behind the cdn. At this point the only thing OP could do is to create a rule to redirect to .nyud.net link if the referrer equals HN. [1] http://news.ycombinator.com/item?id=2235559 http://news.ycombinator.com/item?id=2235559

dspillett 16y ago
At this point the only thing OP could do is to create a rule to redirect to .nyud.net link if the referrer equals HN. At this point there might be nothing the OP can do except wait until the initial hump of traffic has died down: ifthe server really is completely bogged down he may not even be able to open SSH session to make any config changes. For an article like this, that does not need any dynamic content, would be better served by an event based server as these tend to cope better on low-end boxes in the presence high demand for static content than thread or process based servers. Or, like you say, stick with the current web server setup and post links to high volume sites via a cache like CoralCDN.
- deno 16y ago
  > At this point there might be nothing the OP can do except wait until the initial hump of traffic has died down: ifthe server really is completely bogged down he may not even be able to open SSH session to make any config changes. I actually did some testing at that moment, before I edited the part you have quoted (I added this later), and I'm confident OP could have probably rescued it if he wanted to. But I agree, it's pretty much game over because you can't edit the link after you've submitted it. So if you're not prepared to handle dense traffic, it's a good idea to submit coralled link instead or put your website behind CloudFront temporarily.