"Ottmar Freudenberger" <> schrieb:
> There definitly seems to be an issue with WU/MU *site* "only".
Just for the doubters:
A short session overview from Fiddler2. Windows XP SP3, IE8, Cache
cleared before running the test, DSL 16Mbit/s. The test consists of
choosing "Windows Update" from the Security -ehm- menu out of IE8,
no scanning etc, just the plain WU site:
Request Count: 84
Bytes Sent: 81.773
Bytes Received: 612.964
ACTUAL PERFORMANCE
--------------
Requests started at: 20:36:11:9531
Responses completed at: 20:38:28:4218
Aggregate Session time: 00:02:51:3437
Sequence (clock) time: 00:02:16.4687500
DNS Lookup time: 312ms
TCP/IP Connect time: 2.999ms
RESPONSE CODES
--------------
HTTP/200: 84
RESPONSE BYTES (by Content-Type)
--------------
application/octet-stream: 22.206
application/x-javascript
: 407.416
text/html: 79.387
image/x-icon: 25.214
text/css: 17.863
image/jpeg: 26.210
~headers: 23.055
text/plain: 218
image/gif: 11.395
As you can see, it took >2 minutes this time to just get the WU site
displayed in IE. I've saved the Fiddler session (and the nXpert report
too).
Some examples? Okay, here we go:
GET /windowsupdate/v6/default.aspx HTTP/1.1
ServerGotRequest: 21:02:19:2500
ServerBeginResponse: 21:02:40:9531
= ~21 seconds
GET /windowsupdate/v6/default.aspx?ln=de HTTP/1.1
ServerGotRequest: 21:02:41:2656
ServerBeginResponse: 21:03:03:7812
= ~22 seconds
GET /windowsupdate/v6/shared/js/resultslist.js?633857617[snipped] HTTP/1.1
ServerGotRequest: 21:03:04:2968
ServerBeginResponse: 21:03:27:7500
= ~23 seconds
GET /windowsupdate/v6/shared/js/spupdateids.js?633857617[snipped] HTTP/1.1
ServerGotRequest: 21:03:04:8125
ServerBeginResponse: 21:03:27:0312
= ~22 seconds
GET /microsoftupdate/v6/shared/js/webcomtop.js?633857617[snipped] HTTP/1.1
ServerGotRequest: 21:03:06:7812
ServerBeginResponse: 21:03:30:2031
= ~23 seconds
GET /microsoftupdate/v6/toc.aspx?ln=de HTTP/1.1
ServerGotRequest: 21:03:31:0000
ServerBeginResponse: 21:03:48:2343
= ~17 seconds
GET /microsoftupdate/v6/shared/js/tgar.js?633857618[snipped] HTTP/1.1
ServerGotRequest: 21:03:51:1875
ServerBeginResponse: 21:04:10:7500
= ~12 seconds
In total ~140 seconds it took for several actions until the
server(!) responded to client's (browser / IE) requests.
> I urge users running into the "slow" Windows Update site reaction to
> contact Microsoft Support and open a call (which is free):
> https://support.microsoft.com/oas/de...prid=6527&st=1
Yeah,
Freudi