3 ms·

This needs an explanation why the requests are so expensive. 39M Requests for $370/Month is an order of magnitude more expensive then the average web applicati

by TekMol 9y ago

This needs an explanation why the requests are so expensive. 39M Requests for $370/Month is an order of magnitude more expensive then the average web application. I read through the article and it did not give any explanation except that it hints at a big database: "database had grown to store a massive slice of the internet". Without actual numbers and a description of the workload, it's hard to say if the described solution is good or bad.

bluedino 9y ago
Did you read the second sentence in the article? You'll get a kick out of it. >> How We Reduced Our Hosting Costs by Two Orders of Magnitude So it was costing them that much more, before. Wow.
brightball 9y ago
That was the first thing that jumped out at me too. Without sharing the portion of the cost that was from having a massive database and associated expenses (storage, redundancy, backups, disk I/O, maintenance) and then not having one at all on the new setup, the savings come across as disingenuous. I wouldn't be shocked if the DB was at least 2/3 of it.
gravypod 9y ago
Just for context at 39M requests at $370 you are spending ~0.001 cent per request. That's only counting the API. That's not counting their Database costs (which if they are archiving a large part of the internet would be sizable). For reference I've had times where I was getting ~1000 requests/day/site on a $17/year VM. This was done with Cloudflare caching and caching PHP output. This comes out to... * `ls /var/www/ -1 | wc -l`: 17 * (1000 * 30 days) = 30000req/month/site = 30k * 17/month * 17 / 12 = $1.5/month 0.00029411764 cents / request That means my request, on a crappy VPS serving Wordpress, some custom static sites, and a few other services (PayPal API handling, emailing, uptime monitoring, etc), cost only 30% as much as the requests described in this post! PHP-FPM, Lighttpd, and MySQL's small config are magical.

by TekMol 9y ago

bluedino 9y ago

Did you read the second sentence in the article? You'll get a kick out of it. >> How We Reduced Our Hosting Costs by Two Orders of Magnitude So it was costing them that much more, before. Wow.

brightball 9y ago

That was the first thing that jumped out at me too. Without sharing the portion of the cost that was from having a massive database and associated expenses (storage, redundancy, backups, disk I/O, maintenance) and then not having one at all on the new setup, the savings come across as disingenuous. I wouldn't be shocked if the DB was at least 2/3 of it.

gravypod 9y ago

Just for context at 39M requests at $370 you are spending ~0.001 cent per request. That's only counting the API. That's not counting their Database costs (which if they are archiving a large part of the internet would be sizable). For reference I've had times where I was getting ~1000 requests/day/site on a $17/year VM. This was done with Cloudflare caching and caching PHP output. This comes out to... * `ls /var/www/ -1 | wc -l`: 17 * (1000 * 30 days) = 30000req/month/site = 30k * 17/month * 17 / 12 = $1.5/month 0.00029411764 cents / request That means my request, on a crappy VPS serving Wordpress, some custom static sites, and a few other services (PayPal API handling, emailing, uptime monitoring, etc), cost only 30% as much as the requests described in this post! PHP-FPM, Lighttpd, and MySQL's small config are magical.