By default Windchill is configured to capture execution metrics of all SQL statements sent to the database. This data is used to populate some logged data (like the MethodServer Summary line, and other JDBC centric JMX measures) and is used by Windchill profiler as well. The downside is the property is CPU intensive and can impact responsiveness of the Windchill server, although I'm not aware of any studies to test it's impact the last numbers I saw were a ~20% overhead on a ~16 second operation. For sites using the PSM the JDBC data being captured by this property may no longer necessary too.
db.property: wt.pom.traceTiming.enable
The default setting is true, disable the tracing by setting the property to false.
This posting is not a recommendation to set this property to 'false' on a production server but rather to share that this setting can have an impact on overall Windchill performance and to encourage testing and the sharing of those results in the comments section.
