Slashdot Mirror
OnLive Latency Tested
The Digital Foundry blog has done an analysis of recently launched cloud gaming service OnLive, measuring latency across several different games. Quoting:
"In a best-case scenario, we counted 10 frames delay between button and response on-screen, giving a 150ms latency once the display's contribution to the measurement was removed. Unreal Tournament III worked pretty well in sustaining that response during gameplay. However, other tests were not so consistent, with DiRT 2 weighing in at 167ms-200ms while Assassin's Creed II operated at a wide range of between 150ms-216ms. ... OnLive says that the system works within 1000 miles of its datacenters on any broadband connection and recommends 5mbps or better. We gave OnLive the best possible ISP service we could find: Verizon FiOS, offering a direct fiber optic connection to the home. Latency was also reduced still further simply due to the masses of bandwidth FiOS offers compared to bog standard ADSL: in our case, 25mbps."
And with the bandwidth this service uses, you'll hit your ISPs "unlimited" cap in what, 6 hours? A day?
The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
The statement is silly because latency isn't directly related to bandwidth. Switches, bridges, repeaters, modems, routers and other such devices all add latency. If FiOS reduces the number of these in the chain, the latency will be reduced. I'm not saying it necessarily does - just that it could provide better latency without having more bandwidth because of other factors.
As an early adopter (read: 1-year free trial ;) the service works fine (6Mb cable conneciton). For twich games you will notice a little sluggishness, but overall, its not difficult to adjust. Essentially, all the games play like a good latency online game. The only thing i'm not sure I like at the moment is the some of the minor artifacting you'll see due to the video compression. Again, this only really comes into play if you stop and look for it, during action you'll not notice it too much as you'll be busy paying attention to other things ;). Though right now, I cant say for sure how this service will perform in the future, as you apply for entrance into the service currently. Once anyone can join whenever they want, its hard to say how quickly OnLive will adjust to increased congestion.
I love to slaughter the english language.
Latency was also reduced still further simply due to the masses of bandwidth FiOS offers compared to bog standard ADSL: in our case, 25mbps.
Damn it, kids, Latency and bandwidth are not the same thing and anybody who makes that mistake should be forced to use a "1Gb/s" connection via fedex.
Yes, in the case of something like OnLive, which is basically streaming mouse/keyboard events one way and video the other, things will look substantially worse if frame N hasn't finished downloading by the time frame N+1 is ready for transfer(and then either has to be dropped, or delays frame N+1 even more than your connection's latency would); but having a fat pipe does not "reduce your latency". It is correct to say that 25mb/s FIOS is probably about the most generous test that is also remotely realistic for more than a tiny number of their potential customers; but the bandwidth thereof does not "reduce latency"...
150-200 ms latency in a modern FPS is nearly unforgivable. I played TF2 a lot for a while and if I ever had more than 40-70 ms latency the hit detection would start to suffer and you'd get shot through walls or just not hit.
I expect a system like OnLive might work better with strategy games and other types of games that are not nearly as fast paced as most modern shooters are.
Admit nothing. Deny Everything. Make Counter-accusations.
In the UK there aren't many options at all. Eurogamer.net is UK-based, hence the mention of BT.
My company don't want the expense of using leased line and other specialist stuff, just an ordinary thing that can work like a home package over an ordinary phone line. The FASTEST damn thing we can have is a single or multiple ADSL2 lines. We have basically unlimited funds for such things and often specify overkill-measures (i.e. 3 or 4 ADSL2 lines from seperate suppliers rather than 1 leased line). We get 20Mbps sync and a little less real-world speed. We are approximately 10 metres from the exchange. We are in an affluent and well-populated area of London.
In terms of what the average home user can have, only Virgin media fibre really beats the other offerings but that's highly variable and although you are told "up to 50MBps", the infrastructure isn't there to give you that as usable bandwidth.
To be honest, I'm impressed they managed to get what they did considering the state of UK broadband. Of course, you can pay stupid money and get serious pipes put in but that's hardly a "real world" scenario for the average home user. It's not unimaginable, though, that a true gamer might have the best a home user can be offered - which in the UK is a 25/50Mbps fibre service.
Remember they don't just send the inputs there. They have to get the display back again.
If each frame is 100Kilobytes and they need 30fps to look smooth that's approaching the limit of 25Megabits/s (=3.125Megabytes/s).
Less than 5ms is nonsense (a simple framerate calculation , but Digital Foundry did quite a few input lag tests.
Anywhere from 60ms to over 100ms is common. Apparently gamers start to notice input lag at 166ms. Also, input lag and network lag shouldn't be confused with each other. The ping values you see in your game aren't 1-on-1 comparable to the input lag rates reported here.
To be honest, the 150ms input lag surprises me in a positive way. It's much lower than I had expected. For a game like UT3, 150ms is probably way too much and apparently that's one of the faster games, so OnLive's input latency is probably still too high for most games.
Wen you see "I am connected to a server, and I have 200 ping with this server", that is not input latency. You can have 10ms input latency with a server that give you 200 ping. Things are computed clientside. So this will be much less playable than your average 200ms server.
-Woof woof woof!
It's not about consoles only. Your PC has the same problem. An average input lag of 5ms is impossible because when you take a game that renders at 60fps, every frame is roughly 16ms on the screen. If you push a button, then your action won't be visible until the next frame. So I'd say that at 60fps you'd have an average input lag of 8ms and that's not taking into account factors like game code processing the input and updating the gamestate or the lag caused by your LCD display.
(Older) PC games can be run at higher framerates because the hardware can handle it, so that might potentially decrease that 8ms average, but 5ms is only achieved with a 100fps framerate (when you assume 5ms as average, if you assume it's the slowest it'll ever be then you need 200fps).
Again, your LCD display has an inherent delay of 40 - 80 ms as well. The idea that 40ms input lag turns a game unplayable is a grave error. I mean, the article already points out that 60ms is basically as low as input lag on a non-LCD screen goes.
Let's assume you have a hop where distance/c = 10ms and packet's length/bandwidth = 10ms. This means, the head of a packet arrives in 10ms, the tail in 20. No routers or bridges save for the most unaware repeaters will handle the packet until it arrives completely. Only then they will examine it and start sending it forward.
Thus, the final latency will be:
a) distance/c, plus
b) time spent in queues, plus
c) time needed for the bodies of packets to arrive.
To reduce a), you need to be closer to your destination. To reduce b), you need an ISP who oversells less. To reduce c), you need bandwidth on all hops.
The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.