test content
Logo
What is the Arc Client?
Install Arc
Arc's not the problem, the Overlay is
oneandonlyrecce
Member Posts: 0 Arc User
Have finally taken the plunge to check out Arc. It's been on my TODO to see what files are being accessed by this thing as I know this is a concern to people. Luckily I have enough IT know-how to avoid another 12Gb download on my 900 kilobit connection.
The game fires up and I quickly flick over to the overlay. Nothing really exciting so back to the game and I'm hitting some serious lag. A quick check show that GameClient has it's 6 TCP connections (2 remote and 4 loopback) and Arc seems sensible with 1. But the Arc Overlay is a different story.
The Overly has between 32 and 36 TCP connections to a small collection of remote addresses on a selection of ports. And some of these connections have a latency over of 600ms. OK that explains the lag. It takes a while but finally the Overlay closes it's connections until nothing is left and the game is playable again
Just to put the 600ms into perspective, using the NetGraph command, GameClient is averaging a 120ms to 140ms latency.
I'm not sure if the overlay really requires all the network connections up-front, or some one hasn't Googled for the phrase "lazy loading", but this sort of load is a pain for someone who's not on a FTTC network.
GameClient doesn't require much in the way of network resource and it's the sodding game. That the Overlay is such a network resource hog is ridiculous.
You're pushing Arc hard, you need to make sure it's ready and backend properly provisioned to cope with demand.
I think I'll be switching back to Steam for the time being.
FYI, monitoring of the network resource usage was done using the "Resource Monitor" built into the OS.
The game fires up and I quickly flick over to the overlay. Nothing really exciting so back to the game and I'm hitting some serious lag. A quick check show that GameClient has it's 6 TCP connections (2 remote and 4 loopback) and Arc seems sensible with 1. But the Arc Overlay is a different story.
The Overly has between 32 and 36 TCP connections to a small collection of remote addresses on a selection of ports. And some of these connections have a latency over of 600ms. OK that explains the lag. It takes a while but finally the Overlay closes it's connections until nothing is left and the game is playable again
Just to put the 600ms into perspective, using the NetGraph command, GameClient is averaging a 120ms to 140ms latency.
I'm not sure if the overlay really requires all the network connections up-front, or some one hasn't Googled for the phrase "lazy loading", but this sort of load is a pain for someone who's not on a FTTC network.
GameClient doesn't require much in the way of network resource and it's the sodding game. That the Overlay is such a network resource hog is ridiculous.
You're pushing Arc hard, you need to make sure it's ready and backend properly provisioned to cope with demand.
I think I'll be switching back to Steam for the time being.
FYI, monitoring of the network resource usage was done using the "Resource Monitor" built into the OS.
0