3 ms·
On scaling from 40 visitors a day to 6 every second
- antihero 14y agoHow badly does your app have to be coded that it can't handles six requests per second? Are they not caching anything?
- jgrahamc 14y agoIt's not 6 requests per second, it's six visitors per second. The issue they faced was that they had very few server resources (a 2 core VM from their university) and the site serves a large amount of graphics in the form of map tiles. In the first 24 hours they server about 2.7TB of data (or a continuous 250Mbps).
- jimwalsh 14y agoThis article lacks substance. Describe in detail what their setup was, what tweaks they made. Just saying it got slow and they added Cloudflare just makes it a bad article. Everyone knows a CDN can help. CDNs arent a magic bullet though, and it would be nice to see the technical side of things that were done.
- tedchs 14y agoSummary: Our server was too small to handle our app's unexpected load; we then sprinkled on magic Cloudflare sauce and it got better.
- dsl 14y agoCloudFlare is the new wp-cache.
- deleted 14y ago[deleted]
- antr 14y agoMaybe Dan reads/answers this: 1. Who hosts Bomb Sight / what kind of solution does the site use? 2. When you say "we managed to squeeze a bit more capacity out of it" what kind of numbers from pre-to-post "squeeze" are we talking about?
- nasalgoat 14y agoTL;DR - Get a CDN.
- masukomi 14y agocorrection: tl;dr get better developers. If your app can't support 6 visitors per second without caching / cdn you're doing something very wrong.