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.
 

Vista 64-bit, Launcher takes 1.5 hours to patch a tiny patch

First post
Author
Previous Topic Next Topic
Heimer
Republic University
Minmatar Republic
#1 - 2012-03-21 13:48:40 UTC
Hello.

On today's small patch, one machine took a couple minutes, another machine took 1.5 hours.

Here is launcher.log. http://pastebin.com/eJMufNGY Started at 5:10, 34 minute delay, then another 27 minute delay, then another 11 minutes to finish up.

Clearly broken.

Any help would be appreciated.
Astrid Stjerna
Sebiestor Tribe
#2 - 2012-03-21 17:03:19 UTC
Heimer wrote:
Hello.

On today's small patch, one machine took a couple minutes, another machine took 1.5 hours.

Here is launcher.log. http://pastebin.com/eJMufNGY Started at 5:10, 34 minute delay, then another 27 minute delay, then another 11 minutes to finish up.

Clearly broken.

Any help would be appreciated.


What're the specs of the systems in question? Have you run a Disk Cldeanup or defragmented your HDD lately? Were they both downloading from the same connection?

Just because things are acting odd does not guarantee that the issue is on CCP's end.

I can't get rid of my darn signature!  Oh, wait....
Heimer
Republic University
Minmatar Republic
#3 - 2012-03-21 17:12:34 UTC

Yes, of course they were using the same connection. In sequence. Computer 1 run the launcher, 1 minute later it was done. Computer 2 then ran the launcher, taking 1.5 hours. This qualifies as a WTF 1.5 hours.

Specs of the slow system:

Quad core CPU.
8GB Memory.
423GB of disk used on a 1TB disk.
Vista Home Premium 64-bit.

Guess what? Not a bloody hardware issue.

Cleaning my disk and defragging it? Oh, yes, of course, complete with replacing boot.ini and reinstalling the OS from scratch.


CCP's program is faulty. Of course there may be something about my installation that is making it slow. What I'm hoping for is for some dev to provide a switch to log what is causing the 1.5 hour delay, not some idiot to propose that I need to defrag my disk.
Heimer
Republic University
Minmatar Republic
#4 - 2012-03-21 17:16:39 UTC
Also, repair.exe suffers from a similar sluggishness.
Heimer
Republic University
Minmatar Republic
#5 - 2012-03-21 17:24:36 UTC
Seriously:

Disk Defragmenter.

[x] Run on a schedule.

Run at 1:00 AM every Wednesday

Last run 3/21/2012

Next Scheduled run: 3/28/2012



(Plainly: the defrag completed running 2 hours before I ran the slow launcher.)
Heimer
Republic University
Minmatar Republic
#6 - 2012-03-23 07:35:46 UTC
Today's launcher-only patch? 1 hour 20 minutes to complete. http://pastebin.com/nRJvnM18
Heimer
Republic University
Minmatar Republic
#7 - 2012-03-30 20:11:28 UTC
The past three patches; today's, the launcher only patch, and the one before that each exhibit the problem of taking 1.5 hours to patch.

Guess I'll log in each and every time a patch comes that takes 1.5 hours to patch and post here.

Could you at least not update the launcher except during downtime so I don't get a ``surprise no game for you for 1.5 hours'' during the day? Thanks!
Heimer
Republic University
Minmatar Republic
#8 - 2012-04-25 20:50:48 UTC
approximately 9 hours to install the inferno patch: (log at pastebin)
Heimer
Republic University
Minmatar Republic
#9 - 2012-04-26 22:46:46 UTC
1 hours, 5 minutes to install the (tiny) Escalation to Inferno 1.0.1 patch: http://pastebin.com/rHehnXep
CCP Cascade
#10 - 2012-04-27 10:14:42 UTC
This is most likely because your firewall/router/antivirus software is blocking the update mechanism. There is currently a known issue with ESET Smart Security which makes the update stall at “Downloading recipes: initializing…” for a really long time.

This sounds extremely similar.

Associate Technical Producer - Core Technology Group
Lors Dornick
Kallisti Industries
#11 - 2012-04-27 11:34:15 UTC
I had a similar issue on my backup rig.

Both downloading and patching took an absurd amount of time and the rig was more or less unusable during this (several hours for the main upgrade) time.

After some digging in the process view I found the culprits.

1. I had realtime monitoring active in Microsoft Security Essentials intercepting all disk access.
2. The hdd driver had for some obscure reason downgraded to PIO instead of UDMA 6 multiplying the delays caused by #1.

Looked a bit strange in the process view showed that nothing seemed to be very active, except the ordinary 'system sleep/wait' process. But when I added the IO columns to the list it became obvious.

Both patcher and msse had a gazillion (almost) of IO requests bombarding the kernel, and with the disk in PIO the system became totally bogged down by it.

So, if the patching takes for ever.
1. Disable any active/realtime antivirus (or similar) software.
2. Check that the driver to the disk (or diskcontroller) hasn't fallen back to PIO.

CCP Greyscale: As to starbases, we agree it's pretty terrible, but we don't want to delay the entire release just for this one factor.