News for hackers. Stuff that matters.
Re:Lots of bugs in 32-bit x86 Linux entry code by srgpqt on Thursday December 12, 2019 @06:29PM (#21777686)
1GB is still a lot of memory. If anything, we've only learned to squander all available memory.
Re:Lots of bugs in 32-bit x86 Linux entry code by IvyMike on Thursday December 12, 2019 @09:43PM (#21778724)
> If anything, we've only learned to squander all available memory.

If I've learned anything in my computer career, it is that this is an evergreen comment. I remember reading Q-Link posts from Commodore 64 users with this complaint when the wasteful C128 came out.

Re:Lots of bugs in 32-bit x86 Linux entry code by derefr on Thursday December 12, 2019 @07:00PM (#21777865)
Go ahead and buffer 4k video streams to disk, I dare you :) There's a reason that even modern appliance platforms like Apple/Android TV need multiple GBs of memory, and it ain't bloat.
Re:Lots of bugs in 32-bit x86 Linux entry code by hvidgaard on Friday December 13, 2019 @04:38AM (#21780311)
If we aim high and say we need 50mbps of bitrate for 4k HDR, we still only need 6-7mb/s. So buffering 30 seconds is still less than 200mb.

It is entirely possible to make a modern system that use far less than they do today. If you're gaming it's a different beast, but for normal OS and programs it's certainly bloat.

Re:Lots of bugs in 32-bit x86 Linux entry code by mehrdadn on Thursday December 12, 2019 @08:25PM (#21778320)
What are you calling "disk" here? It's not every day that I see a machine with a disk slower than its network connection.
Re:Lots of bugs in 32-bit x86 Linux entry code by eru on Thursday December 12, 2019 @11:34PM (#21779160)
An aside: that's often true in Google's data centres. So much, that someone wrote a system to sort-of swap out memory to other machines' RAM over the network (instead of to disk, which Google doesn't do in general).
Re:Lots of bugs in 32-bit x86 Linux entry code by tedunangst on Thursday December 12, 2019 @09:55PM (#21778764)
That might describe every rpi running off SD.
Re:Lots of bugs in 32-bit x86 Linux entry code by boring_twenties on Friday December 13, 2019 @02:07AM (#21779706)
I dunno, not sure about the latest Pi models but the network performance was horrid on the earlier ones, like 20Mbits/sec tops.
Re:Lots of bugs in 32-bit x86 Linux entry code by Piskvorrr on Friday December 13, 2019 @06:45AM (#21780787)
If you're talking RPi1, perhaps. That's 2012, however...and one of the first things to get better in every further model.
Re:Lots of bugs in 32-bit x86 Linux entry code by trasz on Friday December 13, 2019 @04:05AM (#21780167)
The irony is, on the other end the inverse is true - filesystem cache hit ratio on Netflix servers isn’t particularly high.
Re:Lots of bugs in 32-bit x86 Linux entry code by saagarjha on Thursday December 12, 2019 @07:08PM (#21777903)
I wouldn’t be so sure.
Re:Lots of bugs in 32-bit x86 Linux entry code by vokep on Thursday December 12, 2019 @06:37PM (#21777742)
This. The basic stuff they did back then didn't magically inflate. Except, it seems from afar that thats exactly what happened. But it didn't, and it doesn't have to look like that from afar.