I have a very easy time showing Windchill performance issueson unix/linux OS systems with multiple method servers (foreground and background). We have a Windows 2008 R2 server and I can't show CPU core # to process id (java process). With TOP in unix/linux, its pretty easy generate performance charts against process id to CPU core. We are having a tough time getting/find a monitor with the same simple mapping for our current Windows 2008 R2 64bit Windchill server. If we had this, it would be easy like Linux/unix, to show the business why there are performance issues with our Windows Windchill Server. PTC points me to their PTC dynatrace monitoring tool which does not have this basic functionailty mapping the java process id to CPU core and it's performance.
Everyone knows who has ever have any experience in Windchill that a java process can only run against 1 CPU core. If that process peaks at 100% CPU core #, Windchill has issues. It can be a single foreground or worse background method server. At the same time the overallCPU utilization is only 10% because the rest of the cores are not maxed at 100%.
Does anyone have a Unix Top monitor for Windows that monitors process id to a cpu core #? We tried the basic Windowstask manager and performance monitor. We even triedour ITtool called What's Up Gold. I haven't tried Appdynamics yet, but I'm open to options.
I know it would be so simple to move to Redhat linux, but that is not an option for meright now.
I tried Process Explorer by Sysinternals but it doesn't map the process id to the cpu core #. I know with top in unix/linux, we can create SAR graphical displays of process id against CPU core # with history and so forth. Thus, we can capture when the server is having issues.
cygwin is a great idea and powershell and the mem command. I'll give thata try. Great idea to put a unix emulator on the Windows machine to get the desired monitoring results. As for Jess, yep, java process can jump from core to core based on completion of the thread. That's a given. But, that is exactly what I'm after is to monitor that process id the CPU core #. Most cases, a max cpu core# if there is only 1 java process (Windchill method server) can help with finding the root cause of the issue and demonstrate/educate to the business the cause of the issues. It is so much easier with TOP and unix monitoring tools.
No worries,I'm just trying to show this case to mycompany which I've shown the same thing occur in many companies. I can see the issue occur in Windows process manager performance monitor but can't map the exact process id.
Not trying to diss ya man. You have always been a great help. Right now I'm looking for a very common issue in Windchill which I'm used to having a unix system to display it and you said it exactly. 1 JVM can kill the entire Windchill no matter how many cores you have because it maximizes 1 CPU core and can then tie up your database as well.
We have been in this business to long and need each other to make this product better.
Sometimes the most active request are not the culprit to the problems. The issues can originate from many potential sources:
Like a doctor, Iwould like to get alerted for a problematic issue at a specific point in time and the complete behavior of that process before I start looking at the overall body or average of all the patients. Symptoms be a result of a cascading effect in Windchill caused by an issue(s) of the ones mentioned above. Even the simpliest functions have a performance issue when the system is already bad state.
I'vebeen working with Windchill since 1998/1999 with the best DBAs, programmers, solution architects, system administrators with almost the entire suite of Windchill.It takes the whole team of these experts to make the product better. We have tocare more about the users/customers and how Windchill can help them in terms of business solutions and improving their current working environment with great performing systems.