Windchill sometimes becomes very slow and even lags

[TB_10966080]

"RMI TCP Connection(8187)-10.10.100.42" Id=33142 daemon prio=5 RUNNABLE (in native) Blocked (cnt): 0; Waited (cnt): 3 CPU nanos: 62500000; User nanos: 46875000; Bytes allocated: 1757000 at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:152) at java.net.SocketInputStream.read(SocketInputStream.java:122) at wt.util.WrappedSocket$Input.read(WrappedSocket.java:380) at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) at java.io.BufferedInputStream.read(BufferedInputStream.java:254) - locked java.io.BufferedInputStream@71cf3053 at java.io.FilterInputStream.read(FilterInputStream.java:83) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:549) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:828) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.access$400(TCPTransport.java:619) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$1.run(TCPTransport.java:684) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$1.run(TCPTransport.java:681) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:681) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPool

"ajp-bio-8011-exec-25" Id=18252 daemon prio=5 RUNNABLE (in native)
Blocked (cnt): 47; Waited (cnt): 45
CPU nanos: 14062500000; User nanos: 11484375000; Bytes allocated: 160853576
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:152)
at java.net.SocketInputStream.read(SocketInputStream.java:122)
at org.apache.coyote.ajp.AjpProcessor.read(AjpProcessor.java:312)
at org.apache.coyote.ajp.AjpProcessor.readMessage(AjpProcessor.java:367)
at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:118)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
- locked org.apache.tomcat.util.net.SocketWrapper@49ae3643
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:65)
at java.lang.Thread.run(Thread.java:745)
at org.apache.tomcat.util.threads.TaskThread.run(TaskThread.java:103)
Locked synchronizers:
- java.util.concurrent.ThreadPoolExecutor$Worker@267bef0b

How to improve it. The above and attachments are thread dump information

[HelesicPetr]

Hi @TB_10966080 

First thing is to find a case why the issue appeared.

What action or function could case it.

Anyway usually it is memory trouble.

Increase the assigned Windchill methodserver memory and also it could be database memory issue.

I would increase the database memory. .  

Anyway here is a article that describes how to investigate the performance issues 

CS211412 - Windchill PLM - SQL Server Performance and Scalability

CS123644 - SQL Server performance diagnostic script for Windchill

CS46060 - Where is the Oracle "gather_info_script.sql" located in Windchill

Performance Tuning Windchill servers that manage CAD Documents

Very useful is PTC Diagnostic utility

Windchill Performance Advisor Utility

export the performance information and use the On-Demand System Scan

CS299230 - Suggested technique for collecting Windchill data for analysis in the "On-Demand System Scan"

PetrH

[TB_10966080]

please see the thread dump。java.net.SocketInputStream.read cost many cpu

[rleir]

Petr has a great answer above.  

Are you on Linux? here are commands which check things quickly:

• top (shows how much CPU time and memory is being  used)
• free (shows how much memory is being  used)
• uptime  (shows how much CPU time: load average: google this )

[TB_10966080]

our os platform  is Windows server 2012，sometimes java.net.SocketInputStream

cost lost cpu resource。

Sometimes, all methodservers occur together。

[TB_10966080]

our os platform  is Windows server 2012，sometimes java.net.SocketInputStream

cost many cpu resource。

Sometimes, all methodservers occur together in same time。

[rleir]

Check the Product Support Matrix, I suspect that Windows Server 2012 has dropped off it. But that might not be causing your performance problem.

I would google for something like 'java performance tuning windows server'.  Look for results in Stackoverflow or Serverfault.

[TB_10966080]

please see the thread dump