Community Tip - Have a PTC product question you need answered fast? Chances are someone has asked it before. Learn about the community search. X
Hi,
We are working with Windchill 9.1 and Pro/e Creo 5 (M110) and are facing on some large projects (1100 objects in workspace) long check in times (upto 35 minutes). All caches (ie and java) are cleared and the workspace and pro/e cach are at minimum required, still we face long delay times. There are also no errors in the method server logs, the user has a 1 Gb line and a HP Z220 unit with 12 GB ram.
Any ideas where the bottle neck could be ?
Best regards,
Bernard
Solved! Go to Solution.
It may be useful to use the PTC System Monitor (PSM) if you have it installed to help determine the bottleneck and/or the Windchill Profiler as per Chris' suggestion. Otherwise, you can enable WGM debug logging as per https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS140107 and https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS140108.
It may also be good to get a Fiddler and Wireshark capture to determine if the bottleneck is network-related.
In general, it would be a good idea to open a tech support case for this as we have internal tools to better analyze the WGM debug logs--they can be a bit cumbersome to analyze otherwise.
This could be an issue on the database side, due to long running queries. You could use the Windchill Profiler to capture the issue and check if DB queries are the bottleneck. The instructions for running the Windchill profiler can be found at the below link:
Thank you Chris for the link. The problem does not appears anymore, as soon as it pops up again I will use the profiler. Hope I can deduct the fault from this amount of data comming from the tool...
It may be useful to use the PTC System Monitor (PSM) if you have it installed to help determine the bottleneck and/or the Windchill Profiler as per Chris' suggestion. Otherwise, you can enable WGM debug logging as per https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS140107 and https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS140108.
It may also be good to get a Fiddler and Wireshark capture to determine if the bottleneck is network-related.
In general, it would be a good idea to open a tech support case for this as we have internal tools to better analyze the WGM debug logs--they can be a bit cumbersome to analyze otherwise.
Thank you Lori for the answer and links. I took a quick look to this frofilier tool and this looks to be a tool for specialists. If the problem occurs again I might open a ptc call.