"In September 1956 IBM launched the 305 RAMAC, the first ‘SUPER’ computer with a hard disk drive (HDD). The HDD weighed over a ton and stored 5 MB of data."
Re:This is what a 5MB hard drives looked like in 1956 (note...
by seanp2k2 on Monday December 26, 2011 @05:26PM
(#3394099)
Can you explain how running any other httpd that runs PHP via FastCGI or CGI would be any better? The problem is that they're dynamic pages. The solution is to statically cache the page in question. Since WP has this block in the default .htaccess:
if you just SSH in to the server, cd over to the HTML root, wget the page in question and save the file as the name of the path, it'll statically cache it and instantly alleviate ~95% of the work needed to serve the page.
Dynamic pages are the culprit in /any/ dynamic CMS, and caching is the solution. You could use Varnish, or write/find a memcached plugin, or use redis or whatever other key/value store is trendy at the moment...it's all caching and it's the best way to make dynamic sites fast (besides Cloudflare, which is just "magical" black-box caching)
Edit: TL;DR using nginx or lighttpd or cherokee or webrick or whatever other httpd happens to be trendy this week won't help that much. Properly configuring a caching system will help an order of magnitude more.
Re:This is what a 5MB hard drives looked like in 1956 (note...
by MichaelApproved on Monday December 26, 2011 @04:31PM
(#3393984)
I like reading stories about how careful programmers had to be when writing code so the use of every bit was maximized. Unfortunately, this also lead to the Y2K debacle.
Re:This is what a 5MB hard drives looked like in 1956 (note...
by ars on Monday December 26, 2011 @04:34PM
(#3393988)
I'm not so sure about that. The 3.5 inch form factor has been around for more than 30 years, and I don't see it going away anytime soon because it's a "human" size (about the size of a hand). People are not getting smaller.
We'll fit a lot of more data onto them, sure. But the physical size of the largest/most common hard disk available at that time is unlikely to change much.
Re:This is what a 5MB hard drives looked like in 1956 (note...
by jws on Monday December 26, 2011 @05:32PM
(#3394110)
Interesting theory on things only shrinking until they reach a "human size".
Many things have shrunk: cell phones, thumb drives, wall warts, personal routers/access points, flash lights, inkjet printers…
Some things can not successfully shrink: keyboards, displays…
But there are very few things that have artificially resisted shrinking: Household telephones and credit cards come to mind.
I think hard drives are a component. 3.5" will yield to 2.5" as each drive stores enough data. Smaller platters start to have diminishing returns. Before you know it the whole product will be over run by something solid state and no one will care what the last size of buggy whip was.
Re:This is what a 5MB hard drives looked like in 1956 (note...
by seanp2k2 on Monday December 26, 2011 @05:20PM
(#3394087)
Even if that happens, a page of uncompressed plain-text data will still be small -- that's another "human size" that won't go away any time soon, so this makes me question how much storage we'll really need in the future. Sure, we'll come up with all kinds of interesting ways to use more of it, but with devices becoming more and more "cloud-centric"...will a phone ever needs /terrabytes/ of storage?
"In September 1956 IBM launched the 305 RAMAC, the first ‘SUPER’ computer with a hard disk drive (HDD). The HDD weighed over a ton and stored 5 MB of data."
RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L]
if you just SSH in to the server, cd over to the HTML root, wget the page in question and save the file as the name of the path, it'll statically cache it and instantly alleviate ~95% of the work needed to serve the page.
Dynamic pages are the culprit in /any/ dynamic CMS, and caching is the solution. You could use Varnish, or write/find a memcached plugin, or use redis or whatever other key/value store is trendy at the moment...it's all caching and it's the best way to make dynamic sites fast (besides Cloudflare, which is just "magical" black-box caching)
Edit: TL;DR using nginx or lighttpd or cherokee or webrick or whatever other httpd happens to be trendy this week won't help that much. Properly configuring a caching system will help an order of magnitude more.
We'll fit a lot of more data onto them, sure. But the physical size of the largest/most common hard disk available at that time is unlikely to change much.
Many things have shrunk: cell phones, thumb drives, wall warts, personal routers/access points, flash lights, inkjet printers…
Some things can not successfully shrink: keyboards, displays…
But there are very few things that have artificially resisted shrinking: Household telephones and credit cards come to mind.
I think hard drives are a component. 3.5" will yield to 2.5" as each drive stores enough data. Smaller platters start to have diminishing returns. Before you know it the whole product will be over run by something solid state and no one will care what the last size of buggy whip was.
There's 32gb of storage on my phone, held in an area roughly the size of a dime. It's not a hard disk, but it shows where hard disks are going.