Windchill Cluster Performances Performance Deep-Dive – PSM Reduce Overhead on Windchill Performances (1 of 4) During the Automated Performance Testing/Stressing Campaign using the INT Cluster, we have observed a large PSM* overhead (above 33%) over Windchill. After having performed Hardware and Software Tuning, this overhead is around 10-17% which is matching industry standards (average 15%) PTC Community Thread on this topic: https://www.ptcusercommunity.com/thread/130088?sr=stream Latest Customer Testimony: We recently started using PSM 4.0 with 10.2 M030 and have not seen any performance impact of this. We have not performed a MULG after PSM 4, but the users have not noticed any performance difference. I have experience in using PSM 3.0 with 10.1 M040 for a large global deployment of Windchill as well, we haven't noticed any significant performance (~5% on RT) overhead contributed by PSM in our MULG tests. It is worth reviewing few points Ensure the UEM is turned off if you don't have licenses for that. If you have remote file servers with not so good WAN connectivity, I don't recommend them to be monitored by PSM as it creates a lot of traffic in the network (PSM agent, collector on the fileserver to PSM server) Ensure that you account for the CPU and memory over head by PSM agents and collectors (~5% on CPU, about 50mb per agent) If you are planning to use the same PSM Server for multiple environments, make sure you size it right What we did from a performance perspective were we excluded a few sensors and purepath measures from being captured which are not really relevant to our business use cases. Tuned the advanced agent mapping settings for Agent - sensors/transactions Tuned the incident rules Thank you Binesh Kumar, BARRY-WEHMILLER INTERNATIONAL INT By considering several layers of software and hardware tuning and also a different way to instrument our automated testing tooling (based on JMeter), the Overhead has been decreased to 10-17%, which is a good match with what is observed by many customers (15 to 20% or 10 to 20% according to the size of the Windchill Implementation and the complexity of the Architecture/Infrastructure) This slide deck details the software tuning operations which were applied to the INT Cluster at the time the overhead was very high. This tuning results from dynaTrace Recommendations so that to apply Production settings to PSM (against the OOTB default settings) Hardware tuning was also performed on the PSM Server. Initially PSM 3.0 was running on a 4-CPU and 32GB RAM running on Windows 2008 Server 32-bit. Currently latest instalment of PSM 4.0 is with 16-CPU and 32GB RAM running on Linux x64. PTC Tech Support Recommendation: PSM DB schema should not be located in same instance as Windchill, as it is indeed affecting Performances *PTC System Monitor Windchill Cluster Performances

Windchill Cluster Performances Performance Deep-Dive – PSM Reduce Overhead on Windchill Performances (2 of 4) dynaTrace Software Tuning Analysis was performed from a System Profile of PRD-DR3 which was provided to a dynaTrace Consultant (Laurent Izac) From this System profile Analysis, dynaTrace has strongly advised to consider some tuning layers over the OOTB installation so that to consider production settings. Following screenshots are summarizing various settings which need to be applied on each and every installation of PSM which is considered with a Windchill INT or PRD Cluster JDBC Sensor Tuning Step 1 of 3 Select [Enable aggregation] – This will have the effect to produce only one line in a Purepath for a same SQL Query repeated identically several times Reduce SQL Captured Length: From 4096 to [1024] Windchill Cluster Performances

Windchill Cluster Performances Performance Deep-Dive – PSM Reduce Overhead on Windchill Performances (3 of 4) dynaTrace Software Tuning Analysis was performed from a System Profile of PRD-DR3 which was provided to a dynaTrace Consultant (Laurent Izac) From this System profile Analysis, dynaTrace has strongly advised to consider some tuning layers over the OOTB installation so that to consider production settings. Following screenshots are summarizing various settings which need to be applied on each and every installation of PSM which is considered with a Windchill INT or PRD Cluster Exceptions Sensor Tuning Step 2 of 3 Select [Aggregation enabled]: As for the SQL Requests of the JDBC sensor, this will reduce to one line in the Purepath exceptions which are repeated identically Deactivate [Capture Stacktrace] Windchill Cluster Performances

Windchill Cluster Performances Performance Deep-Dive – PSM Reduce Overhead on Windchill Performances (4 of 4) dynaTrace Software Tuning Analysis was performed from a System Profile of PRD-DR3 which was provided to a dynaTrace Consultant (Laurent Izac) From this System profile Analysis, dynaTrace has strongly advised to consider some tuning layers over the OOTB installation so that to consider production settings. Following screenshots are summarizing various settings which need to be applied on each and every installation of PSM which is considered with a Windchill INT or PRD Cluster Servlet Sensor Tuning Step 3 of 3 Uncheck Option  [Capture details in all filters and servlets] Windchill Cluster Performances