These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
 

1991 Called, they want their internet speed back!
Author
Previous Topic Next Topic
Kikki Di'je
Sebiestor Tribe
Minmatar Republic
#1 - 2014-11-04 18:56:09 UTC
From Repair Tool (Because actual patcher hasn't worked in months):

(6/7) Downloading patch: 92.1%, 200.76 MB/218.07 MB, 2.67 KB/s, 01h50m11s

From Router:

Verizon (MPLS): 1000.00MB Fiber MM BWC 0/1000.00 Current Use: 0.0/1000.00

Y U H8 ME BRO
Zepheros Naeonis
TinklePee
#2 - 2014-11-04 23:17:07 UTC
Not much better on my end. Just started the Phoebe patch and I am barely getting 100KB/s. This has been a common trend with patching EVE the last 6 months or so. I have a fiber optic connection as well.
Theodoric Darkwind
The Scope
Gallente Federation
#3 - 2014-11-04 23:50:27 UTC
Same issue.

Either CCP is using a commonly throttled port or their bandwidth really sucks that bad.

WTB patch mirror
Kaliba Mort
Dark-Rising
Wrecking Machine.
#4 - 2014-11-06 02:26:12 UTC
I diagnosed and reported a bug with CCP about this many many months ago, but either they don't care are not competent to fix the issue their protocol design caused. My patch download speed was a meager 800kbps (that's kilobits, not bytes). The problem has to do with their patcher design. They seem to have a massive mirror of entire EVE as one file, compressed or otherwise (didn't check), but they file is a few gigabytes in size. Probably one giant file per version, so they can "create a patch on the fly". Then what the patches does is,


  1. download a little part of the file that is different between versions
  2. seek to next difference portion to download that.


The result is that they are doing GET requests for about 100kB at a time and then jumping around the 8GB file, treating network as some sort of a random-access resource. CCP doesn't even bother to pre-process this ridicules behaviour between consecutive releases.

The result is the more mirrors you have, the worse this behaviour actually becomes! Fast access relies on the massive patch being in proxy's memory, otherwise you have to wait for the seek and that takes a while. On my connection, I can easily download that big file at max line speed, but because of the way patcher requests little chunks, well, it completely kills throughput.

Thou shalt not use HTTP for random file access

CCP devs don't know, or don't care considering they have done nothing to alleviate this issue. The fix is simple enough - download pre-processed patches, like in the old days, for major releases. Then you are downloading a file sequentially. If CCP wants to fix case of faulty routers breaking large patch integrity (eg. router's bad memory flipping some bits), then they are doing it wrong.

PS. CCP is not using any "throttled ports". They are using standard pipelined HTTP.
Caviar Liberta
The Scope
Gallente Federation
#5 - 2014-11-06 23:10:36 UTC
If we could actually download the patch file manually like we use to then I'd fire up a program like getright and download it over 4 connections.