4 ms·
Well, this is interesting. I've been running http://jsonip.com http://jsonip.com for 4-5 years. Right now, it's averaging 10 million requests a day. I don't
by geuis 11y ago
Well, this is interesting.
I've been running http://jsonip.com http://jsonip.com for 4-5 years.
Right now, it's averaging 10 million requests a day.
I don't do any logging other than total bandwidth usage, in and out. I have been getting numerous noticed from my host because I haven't bothered to update the usage alarm levels. I'll adjust that when it matters.
Basically, I don't give a shit what you're using it for. Only one time in the last 4 years have I had to explicitly take action against an abusive user. If you're the dipshit with the misconfigured squid proxy a few years ago that got the 418 You're a teapot response, you know who you are.
Btw jsonip is a node.js service. It's been working at scale, just fine, and will continue to in the future.
- martin-adams 11y agoThat sounds pretty cool. Out of interest, that works out at an average of 115 requests per second. How many Node servers do you have serving that if you don't mind me asking?
- tbrock 11y agoProbably one. This means it has roughly 8ms/request and likely works because it's not computationally bound.