3 ms·
To be sure! Our expectations of what a computer required to do $task looks like has dramatically changed, too. Last week a coworker was surprised that I deploye
by kstrauser 7y ago
To be sure! Our expectations of what a computer required to do $task looks like has dramatically changed, too. Last week a coworker was surprised that I deployed a tiny service on a t2.nano EC2 instance. "Shouldn't we put that on something bigger?" Well, the thing is entirely blocked on waiting for network IO, so putting it on a server with 32 cores isn't going to make it run any faster. Also, under full load it only used 32MB of RAM, so giving it 8GB isn't going to help it any.
Bringing it back to the RPi: people ask if it's powerful enough to serve simple web apps and email. Oh, it most certainly is! It can handle most of what you'd want a home server to do, short of something like Plex transcoding.
- jmnicolas 7y agoWhy not Lambda then ?
- kstrauser 7y agoIt's a long-running, stateful process. I love Lambda but this wouldn't have been a good fit for it.
- baebeegeezus 7y agoOne of my first jobs in 1997 was as a network admin, setting up an email, web server and firewall for our 100 person office. Used a 486 DX2/66 with 16MB (not GB!) RAM running RedHat, obviously very minimal without X or GUIs. The Internet line was only 128kb/s, so the CPU was underutilized most of the time.
- kstrauser 7y agoHah, much the same here. We were on some sweet Pentium 133s on Debian, and even our blistering fast 4 bonded T-1s weren't enough to make them break a sweat. I know MHz isn't everything, but a 1.5GHz quad-core ARM is abundantly sufficient for running Wordpress and Django and a PostgreSQL backend with plenty of room to spare.