Poor performance in Workspace of 3000 items

[jhengel]

Hello all,

I was talking with a fellow adminand he was describing an issue that one of his
users is having. They just migrated from Ilink 3.4 to PDMLink 9.1. He has a
particular user who is experiencing extremely slow workspace performance. His
workspace is not particularly large, about 3000 objects.
Can you give me some areas he should look at? Maybe config settings, etc. I
don't have all the particulars but I thought you guru's out there might be able
to give us some possibilities.

Thanks in advance!
John
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[pwilliams-3]

John,
We had the same issue with WF 5.0 M070 x64 and 9.1 M050. When the user would open an assembly and subsequently a sub-assembly he would experience wait times between 5 and 15 seconds. When he would work offline on the same assembly the operations would be almost instantaneous. We have opened a ticket with PTC and got an SPR filed. The TSE said that even with a WS of 3000+ objects we should not be seeing a slow down like we are. We have applied the following configuration settings:

compress_output_files yes
dir_cache_max 500
disable_search_path_check yes
dm_cache_limit 0
dm_cache_mode none
dm_http_compression_level 3
dm_network_request_size 1000000
dm_network_threads 4
dm_synchronize_in_background yes

Restart the computer once these settings have been made.

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>

2. Install certified graphics card drivers when available. See table below.


Workstation Model

Windows XP 32-bit

Windows 7 64-bit

Release Date

Version

Release Date

Version

M4300

7/3/2008

175.75 ISV, A06<">http://support.dell.com/support/downloads/download.aspx?c=us&cs=04&l=en&s=bsd&releaseid=R191014&SystemID=WRK_NBK_PNT_P4_M4300&servicetag=&os=WW1&osl=en&deviceid=13675&devlib=0&typecnt=0&vercnt=5&catid=-1&impid=-1&formatcnt=0&libid=6&typeid=-1&dateid=-1&for>





M4400

8/15/2010

6.14.11.8992, A10<">http://support.dell.com/support/downloads/download.aspx?c=us&cs=04&l=en&s=bsd&releaseid=R278379&SystemID=PREC_M4400&servicetag=&os=WW1&osl=en&deviceid=16155&devlib=0&typecnt=0&vercnt=8&catid=-1&impid=-1&formatcnt=0&libid=6&typeid=-1&dateid=-1&formatid=-1&s>





M4500

11/10/2010

6.14.12.5922, A08<">http://support.dell.com/support/downloads/download.aspx?c=us&cs=04&l=en&s=bsd&releaseid=R287179&SystemID=PREC_M4500&servicetag=&os=WW1&osl=en&deviceid=21038&devlib=0&typecnt=0&vercnt=4&catid=-1&impid=-1&formatcnt=0&libid=6&typeid=-1&dateid=-1&formatid=-1&s>

11/20/2010

8.17.12.5922, A08<">http://support.dell.com/support/downloads/download.aspx?c=us&cs=04&l=en&s=bsd&releaseid=R287174&SystemID=PREC_M4500&servicetag=&os=W764&osl=en&deviceid=21038&devlib=0&typecnt=0&vercnt=4&catid=-1&impid=-1&formatcnt=0&libid=6&typeid=-1&dateid=-1&formatid=-1&>

M4600





5/13/2011

8.17.12.6696, A00<">http://support.dell.com/support/downloads/download.aspx?c=us&cs=04&l=en&s=bsd&releaseid=R296493&SystemID=PREC_M4600&servicetag=&os=W764&osl=en&deviceid=26138&devlib=0&typecnt=0&vercnt=1&catid=-1&impid=-1&formatcnt=0&libid=6&typeid=-1&dateid=-1&formatid=-1&>

T3400

12/2/2009

6.14.11.9038, A10 XP32_190.38 with DUP<">http://support.dell.com/support/downloads/download.aspx?c=us&cs=04&l=en&s=bsd&releaseid=R238862&SystemID=PRE_T3400&servicetag=&os=WW1&osl=en&deviceid=14688&devlib=0&typecnt=0&vercnt=7&catid=-1&impid=-1&formatcnt=0&libid=6&typeid=-1&dateid=-1&formatid=-1&so>





T3500





8/21/2009


8.15.11.9038<">http://support.us.dell.com/support/downloads/download.aspx?c=us&cs=04&l=en&s=bsd&releaseid=R229594&formatcnt=0&libid=0&typeid=-1&dateid=-1&formatid=-1&source=-1&fileid=329764>


Creo

1. Implement the settings in the attached config.pro file. Once this is done the user will need to unregister the Windchill server and reregister the Windchill server. This will allow the http_compression_level setting to be recognized.

a. Performance Tuning Recommendations For Client Systems And Windchill Servers That Manage CAD Models<">http://www.ptc.com/appserver/wcms/standards/freefull_cskdb.jsp?&im_dbkey=105413&icg_dbkey=900>

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@01CC4066.C8D780B0]

[DamianCastillo]

Patrick,

You are like Neo from the Matrix. Why in the world is the solution so complex? We are in the process of implementing Windchill 10 and things like this scare me. 🙂

"Too many people walk around like Clark Kent, because they don't realize they can Fly like Superman"

[BenLoosli]

The solution is complex because there are a lot of off-the-shelf components used in Windchill and they require tuning for what Windchill wants. Most of what Patrick outlined is also in a PTC document titled "Performance Tuning Recommendations for Client Systems and Windchill Servers that Manage CAD Models".

[msteffke]

Then off the shelf components should not have been used! These tweaks
are PAINFUL. Tweaking the registry on 60 machines? These are not
solutions, these are like bumpy gravel road detours. But in this case
the closed road is not being fixed. The bridge is out and it being left
that way. Very disappointing.

[davehaigh]

Most of the registry edits are edits to improve the performance of Internet Explorer. Properly configured they improve both the embedded and stand alone browser performance.

PTC does have a couple of utilities that will help you tune Windchill and the Client.

The Windchill Client Inspector & the Windchill Configuration Assistant
You will find both in the software download menus for PDMLink

David Haigh

[MikeLockwood]

We did very little of this, but our performance matches or beats PTC's published world car performance in pretty much every area.

The changes we made are mostly in the database (Oracle):

- Dedicated tablespaces with multiple data files for the largest tables

- Much larger extent sizes for those tablespaces

[BenLoosli]

You can do the modifications to the registry on one machine and then export that portion of the registry hive to copy to other machines and apply.

If you are coming off of Intralink 3.x, Windchill will be an adventure until you understand how it all functions. I am still learning and have been using PDMLink since 2005.

Why not use off-the-shelf products? Should PTC spend resources (people, time and money) developing a web browser just so we can look at Windchill data?
Should they spend resources developing a weblet to serve the web pages?
What about a relational database, directory services, and reporting tools?
PTC needs to spend their resources on developing their products that add value to their business which ultimately helps us users by getting a better product that does what we want faster and easier.

Thank you,

Ben H. Loosli
USEC, INC.

[msteffke]

Did not know you could do that. (export that portion of the registry
hive to copy to) . Sounds rather dangerous, but worth a try.

[DamianCastillo]

Ben,

Thanks for the explanation. It's great to have educated users that are
there to help others. I may need you to answer some questions for me in
the near future. 🙂


Damián Castillo
CAD & Administration Manager
Engineering Department
Hensley Industries

[davehaigh]

Attached is one such registry file. I've change the extension to get past email filters. Just change .piz to .zip

Unzip and then edit the file to see what it's like. Double clicking on it will install on the system.

This is what I consider the minimum set of settings. It doesn't include multi-threaded download because those settings are dependent on the version of IE you are running.

Assuming you don't have these settings, do some testing on how long it takes to fill out a table in a large workspace.
Then double click on the .reg file to load the settings and do the test again. You should see an obvious difference in how long it takes to fill out the table. The settings that makes the most difference are these:

[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

The tpi for these two is here:

[EricHuffman]

I was just wondering if anyone has tried doing this.
I tried and I think things are runny a tad slower so I'm wondering if these settings don't apply to my configuration: WF4 XPx64 and PDMLink 9.0

Thanks,
Eric

[EricHuffman]

Also, with regards to the page file: I have 16Gb of RAM-do I even need a page file?
Thanks,
Eric