4 ms·
I mean it really depends on what your doing. If you’re just serving static content then of course you can get away with one small box. If you have user conten
by charrondev 3y ago
I mean it really depends on what your doing.
If you’re just serving static content then of course you can get away with one small box.
If you have user content that’s being constantly updated and inserted you need a lot more.
You need databases, caches, and in our case elastic search (with ~10 billion documents). The data needs to be indexed 16 ways to Sunday to make sure that a user hitting the page with this filter or that sort selects just the right records.
If you care about reliability you should have read replicas of your DBs as well.
Where are your logs going? I’d expect servers for that as well.
Now alternative to a bunch of this you could just use SaaS products but that costs an arm and a leg.
- feverzsj 3y ago> dynamic pages on the SQLite website typically do about 200 SQL statements each. [0]: https://www.sqlite.org/np1queryprob.html https://www.sqlite.org/np1queryprob.html
- johannes1234321 3y agoHow many of the request on sqlite.org go to the "dynamic pages"? I would assume by far most are on the static docs. The forum and other "dynamic" content is quite hidden.
- SQLite 3y agoAbout 10% overall (9.96% to be precise), according to server logs over the previous 10 days. Robots hit dynamic content at about twice the rate as humans: 14.12% versus 7.8%. About 34% of traffic is from robots, from what I can tell (though to be fair, many robots these days work hard to disguise themselves has human, so the actual percentage of robot traffic is likely much higher.)