cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Did you know you can set a signature that will be added to all your posts? Set it here! X

Translate the entire conversation x

Search performance difference between IE8 Firefox 8 in WC 9.1 M060

custodio
1-Visitor

Search performance difference between IE8 Firefox 8 in WC 9.1 M060

Hi,



Some of our users are reporting poor performance when searching Windchill
9.1 M060 with Internet Explorer 8. If they run the same exact search in
Firefox 8, they get much faster results.



Each user gets the result set in approximately 3 seconds in FireFox. But, if
they user IE, one user gets the result set in 30 seconds and the other in 50
seconds. Again, they are running the same exact search as the same exact
user from the same exact Workstation.



We are digging into the issue and don't have much more information at this
point other then reproducing the issue with the users and verifying their
problem.



Any ideas?



And, no need for comments regarding the FireFox vs Internet Explorer debate.
I fully understand. J



Thanks for any help!



Pat Custodio



2 REPLIES 2
pwilliams-3
13-Aquamarine
(To:custodio)

Have you tuned IE 8 settings???

Windows (Not version specific)

1. Set the system page file using the following formula: (RAM * 2) + 640 MB.

a. TPI 143897<">https://www.ptc.com/appserver/cs/view/solution.jsp?n=143897>

Internet Explorer

1. Modify the registry to increase the http thread count to 10.

a. TPI 135832<">https://www.ptc.com/appserver/cs/view/solution.jsp?n=135832>

Internet Explorer 8.0
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_MAXCONNECTIONSPERSERVER]
"iexplore.exe"=dword:0000000a
"xtop.exe"=dword:0000000a

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_MAXCONNECTIONSPER1_0SERVER]
"iexplore.exe"=dword:0000000a
"xtop.exe"=dword:0000000a

Internet Explorer 7.0
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
"MaxConnectionsPerServer"=dword:0000000a
"MaxConnectionsPer1_0Server"=dword:0000000a


2. Modify the registry to disable the slow script messages.

a. TPI 130854<">https://www.ptc.com/appserver/cs/view/solution.jsp?n=130854>

Internet Explorer 8.0 and 7.0
[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Styles]
"MaxScriptStatements"=dword:ffffffff


3. Modify the registry to improve embedded browser performance.

a. TPI 133412<">https://www.ptc.com/appserver/cs/view/solution.jsp?n=133412>

Internet Explorer 8.0 and 7.0
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Script\Features]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Script\Features\iexplore]
"GcVarTrigger"=dword:00010000
"GcValTrigger"=dword:00010000
"GccbSysTrigger"=dword:00040000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Script\Features\xtop]
"GcVarTrigger"=dword:00010000
"GcValTrigger"=dword:00010000
"GccbSysTrigger"=dword:00040000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Script\Features\ptc_ie_server]
"GcVarTrigger"=dword:00010000
"GcValTrigger"=dword:00010000
"GccbSysTrigger"=dword:00040000


Patrick Williams | Engineering Systems | o: 616.698.3766 | c: 616.947.2110
[cid:image001.jpg@01CCBA67.F5036520]

We found that IE 8 in PDMLink 9.1 will download all HTML results of any
table, such as a BOM or search result, before displaying any results.
However, other browsers, like Firefox, display results immediately as they
arrive from the server causing the results to appear to be faster. We
actually timed the database and application speeds, however, and we found
that the total time to download ALL data was identical for IE8 and
Firefox; but because Firefox started painting the early results almost
immediately, while IE8 waited to get everything before displaying
anything, all users reported Firefox as "faster."

We also found that if you install the Google Chrome Frame for IE8 that IE8
in 9.1 PDMLink starts behaving like Firefox, and appears to be "faster."
Unfortunately, the Google Chrome Frame for IE8 broke a number of our
customized forms. Since Windchill 10.0 does not appear to behave this way
with IE8, and since we are going to 10.0 next year, we are just living
with the problem in IE8 from now until then as opposed to redoing our
enhancements to work with Google Chrome Frame for IE8 or moving to another
browser. If you have no customizations, or none with javascript, then you
might try using the Chrome Frame.

Al Anderson




Announcements

Top Tags