News for hackers. Stuff that matters.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by brenden2 on Monday January 06, 2020 @10:53AM (#21970029)
Stadia is just a bad idea and a bad product. Consumer internet access is nowhere near capable enough for it to make sense.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by axaxs on Monday January 06, 2020 @11:13AM (#21970245)
Can't disagree more. I don't live in a big city. My best guess at where the data center is would be a mid-size city about an hour away, or more likely, a big city about 2.5 hours away (driving time). I didn't have high hopes for Stadia but wanted to check it out. I have zero problems with latency, and never think about it when playing. It does have its bugs...random crashes, a few seconds of LoFi here or there probably due to jitter somewhere...but overall, it really works well for me.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by asdasdasdasdwd on Monday January 06, 2020 @11:31AM (#21970421)
Stadia is a bad product, not because of the technical difficulties but because it makes no sense to pay for a service and then pay for access to the content in that service (the games) and if you stop paying for the service you lose access to the content (for which you payed full price by the way). I wouldn't mind a "Netflix for video games" but Stadia isn't it.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by axaxs on Monday January 06, 2020 @11:41AM (#21970526)
I mean, it's not that different than the current model. With XB1 for example, you lose access to the 'free' games, as well as the ability to play online, if you don't have a monthly subscription. For single player offline games, it might be ok. But Stadia supposedly will have a free tier I think, I don't keep up with its news much.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by mrep on Monday January 06, 2020 @11:33AM (#21970451)
You do know that they are going to release a free 1080p version this year right (although you still have to pay for the games)? You only need to pay the subscription if you want 4k @ 60 fps.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by ddingus on Monday January 06, 2020 @12:14PM (#21970857)
Seems free to play will follow that release, along with AD supported gaming.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by buttersbrian on Monday January 06, 2020 @12:24PM (#21970967)
There is a free tier coming, so you even if you stopped paying for "pro" you would be able to access any games you had purchased.

This is the same as Xbox and PSnow, etc. You have to pay for the service via a game pass or pro membership on top of buying the game and possibly the system before you could stream it.

Even in the case of shadow, you'd have to pay for the service to stream games you'd buy and access off your own/their system.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by siffland on Monday January 06, 2020 @02:01PM (#21971969)
I would not get it for this exact reason. However to counterpoint your argument this will work for some people like my high school kids.

They stream spotify because they don't want to buy songs and after that current song is no longer popular they move on to another one and forget the first song ever existed. They play video games and when they are done they sell them and buy a new one, never wanting to revisit the old one. They spend $50 on the new game and sell it for $15ish. For that mindset of people this is a great product, along with the digital only xbox one.

I am not implying all kids or youth are like this, mine are and a bunch of their friends are. I prefer gog or a physical copy, but then again i don't buy that many games.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by aphistic on Friday January 10, 2020 @12:28PM (#22012734)
That's completely wrong. Any games you paid for are yours to play without any monthly subscription. The monthly subscription does give you access to a free game or so a month that you'd lose access to and you wouldn't be able to play at 4K but you wouldn't actually lose access to the games you paid for.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by justwalt on Monday January 06, 2020 @11:03AM (#21970144)
But the issue isn’t bandwidth, really, is it? I would think the ping would be the killing factor. Do they have a plan for that? Server farms no more than 20ms away from anywhere in the US?
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by cptskippy on Monday January 06, 2020 @11:18AM (#21970294)
>> Consumer internet access is nowhere near capable enough for it to make sense.

> But the issue isn’t bandwidth, really, is it?

No, bandwidth isn't the issue, I believe the op was referring to Latency.

I have 75mbps DSL and the Latency is garbage with 29ms being best case. I get frequent periods of 90+ms latency.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by tudelo on Monday January 06, 2020 @11:25AM (#21970357)
These seem like pretty common latency numbers for online gaming. I guess it feels worse when there isn't the movement prediction and other techniques to make the latency feel better since the game isn't running locally.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by cptskippy on Monday January 06, 2020 @12:07PM (#21970798)
Those latency numbers are just for the connection to a test endpoint optimized for low/zero latency.

My "ping" on games like Battlefield are in the 150+ms range and I frequently get high latency dropped from matches.

When I had Cable my latency was around 15ms and my ping times were 90-120ms in Battlefield.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by cooljacob204 on Monday January 06, 2020 @12:48PM (#21971204)
Well the issue is that you have input lag on your controller inputs. When I move my crosshair it takes a long to actually show the crosshair moving on screen.

In normal online gaming you do not have that issue. When I move my crosshair in cs:go it moves instantly.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by tudelo on Monday January 06, 2020 @02:35PM (#21972332)
Right, yeah that's kind of what I was trying to suggest. Honestly, I don't really see how this can work in the general case all that well given exactly what you are saying. I have seen some examples of fighting games being played over stadia, but many fighting games rely on frame-perfect input (and purists in communities like melee dont even use certain monitors due to this...)
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by the8472 on Monday January 06, 2020 @11:57AM (#21970680)
Some games can be far more demanding than video streaming. HDR content, 4k, >60fps, 4:4:4 chroma (text looks horrible on 4:2:0). The requirement for realtime encoding instead offline encoding also means the codecs get less lookahead (as few frames as possible) which results in higher bandwidth requirements for a certain quality level compared to VoD.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by dada78641 on Monday January 06, 2020 @11:36PM (#21976869)
Absolutely. Doing realtime video encoding is costly as it is, and the kind of hardcore gamers Stadia seems to be marketing for are definitely going to notice this. Some games are absolute codec poison, too.

Check out some of the Games Done Quick runs from last summer on Youtube, for example. A lot of the FPS games especially look dreadful. I'm sure Stadia can do better, but there's only so much bandwidth you can throw at this problem before it becomes untenable: https://twitter.com/dada78641/status/1207751665752911872

To me, the main issue with Stadia is not the product itself but the massive amount of extra CO2 that's generated trying to solve all these issues that were already solved decades ago by having your own cpu in your own personal computer in your own house.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by shadowgovt on Monday January 06, 2020 @11:24AM (#21970347)
You hit the nail on the head. The distribution of local server farms in Google's network is much, much larger than people assume (has been for awhile).

There's also a chicken-egg effect that Google's still interested in for secondary reasons. Reverse the question: assume Stadia takes off and becomes the "killer app" of gaming (big assumption, but still). Will local municipalities continue to tolerate crap networks if it means they're left out in the cold on this thing? Google's still interested in improved network infrastructure and has the clout to play incentive games to make that scenario more likely.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by judge2020 on Monday January 06, 2020 @11:05AM (#21970162)
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by foobiekr on Monday January 06, 2020 @11:30AM (#21970412)
it will be shocking if this actually works without being a glitchy mess. I think it’s mostly an excuse to get people to stop talking about it.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by dada78641 on Monday January 06, 2020 @11:52PM (#21976972)
It exists. RetroArch has it in some cores, for example. It was originally conceived of and made by emulator developers.

Of course, it gets really hairy really quickly. Technically, a perfect runahead/negative latency requires ([all possible input states] to the power of [amount of frames of lookahead]) frames to be rendered.

A single player NES game has 8 binary state controller buttons, so 2 to the power of 8 input states. You need to render 256 frames for each frame of runahead.

Now surely you're thinking you'll just prune the set of possible input states through smart prediction of what the player will probably do next, but it doesn't matter. The number very quickly grows to ludicrous amounts of processing for anything that isn't an antiquated console. Let alone for 3D FPSes that use float values for e.g. mouse state.

Edit: and I should add that if they even try to do this, the amount of CO2 they'll waste is going to be horrifying.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by SmirkingRevenge on Monday January 06, 2020 @11:57AM (#21970684)
They use it in games like thumper. Also, this same technique is already used in many street fighter style fighting games. Its not new - and it works.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by _--___-___ on Monday January 06, 2020 @12:26PM (#21970978)
GGPO (the fighting game rollback implementation) simply predicts that each player's inputs on frame N+1 is the same as frame N. This works well enough for fighting games but may not generalize, especially in games with precise analog inputs. Also, there's a hard requirement that in order to roll back 3 frames the engine has to be able to simulate re-running those 3 within the timespan of one frame, which is sometimes an issue when trying to patch this onto a finished game.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by blihp on Monday January 06, 2020 @11:21AM (#21970315)
It's primarily latency but bandwidth can also be an issue. Assuming you have a fast enough Internet connection (possibly not a safe assumption here in the U.S.), imagine your PC or mobile device(s) decide to update themselves or just generally get 'chatty' while you're playing. I've had this create problems for relatively bandwidth-sipping VoIP sessions so I'd imagine it would be much worse for a game experience.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by mvanbaak on Monday January 06, 2020 @11:59AM (#21970706)
Yes, the problem is latency. Which is actually not that big of a problem in some parts of the world. Also, if you have a metered connection bandwidth can become a problem. I have tested stadia at family and I was really impressed how well it works. Personally I am not going to pay for it and will keep using my consoles, but Stadia certainly works.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by littlestymaar on Monday January 06, 2020 @11:48AM (#21970604)
True but because of bufferbloat[1], bandwidth problems often also materialize as latency problems unfortunately.

[1]: https://en.m.wikipedia.org/wiki/Bufferbloat

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by nabla9 on Monday January 06, 2020 @11:05AM (#21970166)
Google is thinking globally.

Local conditions (US for example) are not necessary a showstopper in Japan, South Korea or parts of Europe. Low latency extremely high bandwidth is the new playground.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by saberience on Monday January 06, 2020 @12:14PM (#21970860)
No it's not haha. I live 20 mins from the center of London and the best broadband I can have at my address is 18Mbit. Yes, Megabits, not Megabytes. And this sort of shit-tier internet is very common in England, Stadia is a non starter for many people here.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by nabla9 on Monday January 06, 2020 @03:56PM (#21973213)
How is that even possible?

I mean, you should get 50 Mbit/s from very affordable mobile broadband. If you have ASDL landline, you can get hybrid solution (combined mobile + landline that works as one) and you should get 100 Mbit/s

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by Kiro on Monday January 06, 2020 @11:45AM (#21970569)
Have you tried it? Works awesome for games like Tomb Raider.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by buttersbrian on Monday January 06, 2020 @12:31PM (#21971037)
It works great on many games. Pro fortnite players would cringe at the latency, but it is good for a large portion of games out there.

I've played Destiny, Thumper, Ghost Recon, Tomb-Raider etc on it and only Thumper was tricky when I tried on a pretty crap connection.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by buttersbrian on Monday January 06, 2020 @12:22PM (#21970935)
Having played games on stadia, I cannot disagree more.

Seems a bit dismissive when MS, Sony, Nvidia, and Google etc having built streaming services that consumers have enjoyed.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by Bayart on Monday January 06, 2020 @11:48AM (#21970605)
As long as you're on fibre, I don't think the link is relevant. You've got much more latency to nibble elsewhere. AFAIK the rendering pipeline is where most of the work is. It certainly seemed that way back when Online was a thing (the first service of this type I can think of).
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by dralley on Monday January 06, 2020 @11:54AM (#21970662)
Not very many people are on Fiber, as a proportion of Google's customer base.

I'm sure plenty of people in this thread have fiber but Hacker News is not really the target audience for Stadia.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by swarnie_ on Monday January 06, 2020 @11:03AM (#21970140)
Stadia requirements:

35 megabits per second: 4K, 60 fps, HDR, 5.1 surround sound.

Consumer internet is fine for this in a lot of the developed world.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by cptskippy on Monday January 06, 2020 @11:21AM (#21970323)
You're missing latency which is arguably more important.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by shadowgovt on Monday January 06, 2020 @11:31AM (#21970417)
Latency is something Google already has a large, distributed network with low-ping datacenters to major population centers to address.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by wolfd on Monday January 06, 2020 @11:36AM (#21970478)
It's hard to beat local compute for latency.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by shadowgovt on Monday January 06, 2020 @12:02PM (#21970740)
Absolutely. One could even make a decent claim that (barring some truly ancient hardware between input, CPU, and monitor / audio circuits) it's impossible.

It's surprising how much latency a human will tolerate without notice, however.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by treis on Monday January 06, 2020 @12:59PM (#21971306)
>One could even make a decent claim that (barring some truly ancient hardware between input, CPU, and monitor / audio circuits) it's impossible.

I think that's only if we ignore monitor refresh rates. Most of us are maxed at 60 FPS which with a lot of hand waving is equivalent to ~17 ms latency. It's relatively easy to get a network with latency better than that. If you can achieve the rendering + data round trip in under 17 ms you're going to be functionally equivalent to a local computer.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by falcolas on Monday January 06, 2020 @11:37AM (#21970486)
Funny, I have around 90ms latency to Google (from my home fiber). So, no, their network doesn't really address it in reality.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by treis on Monday January 06, 2020 @11:48AM (#21970598)
Just because you have bad latency doesn't mean everyone else does.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by falcolas on Monday January 06, 2020 @11:56AM (#21970674)
Given that I'm running fiber that connects to the local university backbone, I'm running the fastest possible link in my area (excepting those in the university).

So, I'd say that I'm running the best case scenario available within my area.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by treis on Monday January 06, 2020 @12:43PM (#21971152)
That's not accurate. A university is a relatively small population and not something that Google will necessarily optimize for. And there's no guarantee that the university isn't doing something wrong that is artificially increasing latency.

My anecdata counterpoint is that I pay for the cheapest/slowest broadband available in a midsized city and my ping to google.com is 14ms.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by orbifold on Monday January 06, 2020 @12:12PM (#21970848)
My ping to google.com is 9 ms at home and around 5 ms at work.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by saberience on Monday January 06, 2020 @12:15PM (#21970876)
I live near London central (20 mins from Oxford circus), the best internet I can get is 18 Megabit, and this is in a relatively modern building (< 15 years old). My situation is not uncommon here in the UK, Internet infrastructure here is terrible. Google Stadia is a non-starter for me.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by crashtec on Monday January 06, 2020 @11:05AM (#21970171)
youd be suprised how alot of people in developed world don't even have access to this
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by jessant on Monday January 06, 2020 @11:09AM (#21970210)
Surprise me, how many people in the developed world don't even have access to this?
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by Supermancho on Monday January 06, 2020 @11:18AM (#21970292)
Most of the seattle area. Anywhere there is only comcast, or frontier or non ATT Uverse fiber in orange county (Orange, Santa Ana, Anaheim, etc. im sure most of irvine is there). I have doubts about shared google fiber in high density housing as well. 35 MB is a big number.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by tssva on Monday January 06, 2020 @11:42AM (#21970544)
35MB is a big number but luckily the requirement is 35Mbs. My experience with Comcast is limited to 2 areas. Northern Virginia where Comcast has competition and rural central Florida where they don't have any. In both locations Comcast is more than able to provide the required 35Mbs even during busy times of the day.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by izacus on Monday January 06, 2020 @11:28AM (#21970386)
So it's not a good product for one US area. What's your exact point?

Product doesn't have to cater to every single place on earth to be viable. It's like arguing that ARPAnet was a terrible product because not everyone had T1 lines.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by swarnie_ on Monday January 06, 2020 @11:37AM (#21970483)
I'm mainly talking about countries with less shitty markets, the US is a glaring and awful exception.

200mb uncapped internet in the UK is super common and pretty cheap (£30-£35 a month), as it is in most of western Europe.

I know this is an america-centric website but please don't apply your standards to us, its terrifying.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by saberience on Monday January 06, 2020 @12:18PM (#21970902)
"200mb uncapped internet in the UK is super common and pretty cheap (£30-£35 a month), as it is in most of western Europe."

This isn't accurate coming from someone living in London. Most of my co-workers do not have access to "200mb" internet and most common is 25mb or less. I personally only get 18Mb on my home connection, i.e. roughly 2MB/sec and this was the best I could get from any provider.

The state of Internet infrastructure is fucking terrible in the UK given how small a country it is. Coming from California to the UK felt like going back in time in terms of Internet speeds.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by SmirkingRevenge on Monday January 06, 2020 @11:43AM (#21970549)
The Stadia requirements state 35 Megabits - not bytes - which is more like 4MB of throughput - and that is just for the 4k stream.

If you can stream video at decent quality, you have the bandwidth for Stadia.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by shadowgovt on Monday January 06, 2020 @11:32AM (#21970431)
FWIW, Seattle's always been behind the curve. I don't know why, but even in the AOL days they were bad relative to the mid-sized east coast town I grew up in.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by swarnie_ on Monday January 06, 2020 @11:38AM (#21970490)
Based on some of the comments i've seen in this thread i'm surprised to hear the AOL days have ended in Seattle.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by chasd00 on Monday January 06, 2020 @11:32AM (#21970435)
35 Megabits/sec is about 4MB/sec
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by yorwba on Monday January 06, 2020 @11:41AM (#21970536)
In 2017, an average 20% of households in the EU did not have access to internet connections faster than 30 megabit/s and a report a year ago found that the original goal of 100% coverage by 2020 would not be reached.

Figure 2: "30 Mbps coverage in all Member States in 2011 and in 2017" https://op.europa.eu/webpub/eca/special-reports/broadband-12...

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by Xylakant on Monday January 06, 2020 @11:40AM (#21970516)
Like half of Germany (+): Select >30 Mbit/sec and see how the map color changes to light blue in many places https://www.bmvi.de/DE/Themen/Digitales/Breitbandausbau/Brei...

(+) only slightly exaggerating

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by yorwba on Monday January 06, 2020 @11:46AM (#21970581)
I have difficulty matching the shades of blue in the legend with those of the map, but I think most areas are at ≥ 75% coverage, no?
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by Xylakant on Monday January 06, 2020 @11:58AM (#21970688)
If you zoom in you'll see that the average is misleading: There's a lot of areas with little coverage hidden in that average. It also includes LTE connectivity which theoretically gives you > 30GB and covers a large area, but practically doesn't.

Germany is pretty bad when it comes to internet speeds. Broken market.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by Arkanosis on Monday January 06, 2020 @11:56AM (#21970673)
You can get cheap 1 Gbps wired Internet in France, yet, in the 5 cities I've lived since 2016: - I actually have > 100 Mbps in 2 of them (both in the 20 biggest cities); - I painfully had > 5 Mbps in 1 of them (in the 20 biggest cities) - I painfully have > 500 kbps in 2 of them (much smaller cities, but still in big urban areas).

I assume France is in the developed world as of 2020 and I believe I've more luck wrt Internet than most people here.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by falcolas on Monday January 06, 2020 @11:40AM (#21970515)
Most of America that isn't in a major coastal city. Cable internet promises more, but it's a shared backbone that is not properly provisioned in most locations during primetime. Streaming from Netflix and YouTube in 1080p is problematic in many of those areas.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by jessant on Monday January 06, 2020 @03:54PM (#21973195)
To pick a state as an example, Iowa speed tests had a mean download speed of 71.39 Mbps in 2018. That is twice what Google says is the requirement for 4k Stadia. So even if prime time speeds are lower, there is still a healthy margin.

https://www.speedtest.net/reports/united-states/2018/#fixed

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by ecmascript on Monday January 06, 2020 @11:42AM (#21970543)
I have 250/100 mbit/s, my brother has 1000/1000 mbit/s. Both are included in our rent.

I don't like Stadia for other reasons but saying that consumer access is not capable because you live in a country that sucks on that part is not really a good argument.

Do you think modern cars are a bad idea as well because there are parts in Africa that doesn't have good roads?

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by jokoon on Monday January 06, 2020 @12:25PM (#21970970)
Mmmh for stadia to work well, the bandwidth necessary is pretty high.

Unless you have fiber, it's not worth it. Some DSL internet still suck today.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by SmirkingRevenge on Monday January 06, 2020 @12:47PM (#21971190)
> Unless you have fiber, it's not worth it.

You don't need fiber. Feels as good as local play on my 220 Mbps down/15 Mbps up internet.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by jokoon on Monday January 06, 2020 @05:24PM (#21974149)
you have that without fiber? without DSL?

anyway most users don't have such a high bandwidth...

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by SmirkingRevenge on Monday January 06, 2020 @10:29PM (#21976547)
Megabits, not bytes, if that's what you are thinking. That's about 27 MBps down and a lousy 1.9 MBps up. Decent, but its not even close to fiber.

And I don't think its particularly greats bandwidth... just about every medium/major metro in US is going to have comparable internet or better.

Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by jokoon on Tuesday January 07, 2020 @05:08PM (#21985579)
I know. 1.9MB/s is still a very good DSL. Many users don't have such good bandwidth.
Re:Linus Torvalds: Linux Scheduler Not to Blame for Google S... by ecmascript on Wednesday January 08, 2020 @10:27AM (#21992194)
What I am saying in northen europe where I live, it's uncommon not to have access to fiber.