5 ms·

We're all assuming content comes in constantly, but that's not the case. I imagine they spike heavily at peak times, perhaps 5-6 fold (judging by my own site s

We're all assuming content comes in constantly, but that's not the case. I imagine they spike heavily at peak times, perhaps 5-6 fold (judging by my own site statistics). Serverless might be good for them because they can handle small loads with small costs and large loads with no effort.

fweespeech 9y ago
> We're all assuming content comes in constantly, but that's not the case. I imagine they spike heavily at peak times, perhaps 5-6 fold (judging by my own site statistics). Serverless might be good for them because they can handle small loads with small costs and large loads with no effort. No. I've pushed 1000 r/s (approx) on a price tracking tool at work for keeping track of competitors on one of those boxes. Their largest spike (even if you assume its 10x their average) would be at most 15% of that.
- codefined 9y ago
  Wow, I wonder if it's location based. Mine was heavily situated in one location, whereas yours was perhaps global? So it was always prime time for someone? Here is a graph of my usage for the past week (note lows of 30-40 and highs of 650 odd): https://puu.sh/wrAn1/5816d3f7d7.png https://puu.sh/wrAn1/5816d3f7d7.png
  - fweespeech 9y ago
    > Wow, I wonder if it's location based. Mine was heavily situated in one location, whereas yours was perhaps global? So it was always prime time for someone? Here is a graph of my usage for the past week (note lows of 30-40 and highs of 650 odd): A) I'm not sure "one location" is a city, country, or province. B) Yes, it was global as we had offices from China to the EU. C) Given the OP is handling 15 r/s, 150 r/s is not going to be pushing 500 mbps unless something is very poorly designed. D) Even at spikes of 40x, it would still only be 600 r/s which is still quite doable with a commodity server. The only serious difference is it was very large batches of requests (20 * SKUs) so people were fine with waiting a few minutes.

fweespeech 9y ago

> We're all assuming content comes in constantly, but that's not the case. I imagine they spike heavily at peak times, perhaps 5-6 fold (judging by my own site statistics). Serverless might be good for them because they can handle small loads with small costs and large loads with no effort. No. I've pushed 1000 r/s (approx) on a price tracking tool at work for keeping track of competitors on one of those boxes. Their largest spike (even if you assume its 10x their average) would be at most 15% of that.

codefined 9y ago
Wow, I wonder if it's location based. Mine was heavily situated in one location, whereas yours was perhaps global? So it was always prime time for someone? Here is a graph of my usage for the past week (note lows of 30-40 and highs of 650 odd): https://puu.sh/wrAn1/5816d3f7d7.png https://puu.sh/wrAn1/5816d3f7d7.png
- fweespeech 9y ago
  > Wow, I wonder if it's location based. Mine was heavily situated in one location, whereas yours was perhaps global? So it was always prime time for someone? Here is a graph of my usage for the past week (note lows of 30-40 and highs of 650 odd): A) I'm not sure "one location" is a city, country, or province. B) Yes, it was global as we had offices from China to the EU. C) Given the OP is handling 15 r/s, 150 r/s is not going to be pushing 500 mbps unless something is very poorly designed. D) Even at spikes of 40x, it would still only be 600 r/s which is still quite doable with a commodity server. The only serious difference is it was very large batches of requests (20 * SKUs) so people were fine with waiting a few minutes.