4 ms·
I keep getting "server busy". Why share a link if it won't be able to handle the traffic?
by enraged_camel 14y ago
I keep getting "server busy". Why share a link if it won't be able to handle the traffic?
- ColinWright 14y agoSo, every time you share a link, you always test it first to see if it can handle the load? Ah, no, looking at your profile you haven't yet ever shared a link. I can only conclude that you find lots and lots of things that you are eager to share with us, but when you rigorously test them you find that they can't handle the load, so you sadly decline to submit them. Thanks for the feedback. I'll be sure to keep it in mind.
- enraged_camel 14y agoThis is a community for geeks. I believe it is a realistic expectation that one should be wary of sharing with tens of thousands of readers sites that run processor-intensive server-side scripts. (Nice ad hominem, by the way.)
- ColinWright 14y agoThis is a community for geeks ( although there are those who claim otherwise: http://news.ycombinator.com/item?id=4681146 http://news.ycombinator.com/item?id=4681146 ). I believe it is a reasonable expectation that people will want to see things and will understand that sometimes they will need to spread the load. Cutting edge technology sometimes can't handle the load, and geeks will know that, understand, and make allowances. I would have thought that people in this community would want to see new stuff, rather than have it withheld simply because someone thought the server might not be able to handle the load. How can one tell if the server is going to be able to handle the load? Perhaps the owners had anticipated that this would be of interest and were ready to handle it? How could I tell? I think it's a reasonable expectation in a community of geeks that if you are to level criticism at me, then you should offer alternatives and constructive suggestions, and I look forward to your reply as to what one should do when considering submitting a link like this. How would you test it?
- enraged_camel 14y agoI didn't give suggestions on how to test it because I figured someone who knows how to automatically generate regular expressions from examples would also know how to test it under load (or that it should be tested before being made public). It should not be that difficult to simulate simple user behavior, especially since the majority of the functionality in this case is tied to (presumably) one method in the code. Run it 100/1,000/10,000 times simultaneously behind the scenes with a bunch of test examples and see if your server vomits. Pretty easy. Honestly, I'm a bit dismayed that you are challenging me on this. "Load-test your code before releasing it" should be a strict requirement for anything that is submitted here. Otherwise, how are people expected to give feedback? Why is our time being wasted on stuff that does not work?
- ColinWright 14y agoHmm. You do realize, do you not, that it's not my code. Or my server. I'm just sharing something I found.