PMS10 on Win2008R2-SP1 - java.exe uses 50-100% CPU

Hello.

I recently migrated our PMS9 to a freshly installed PMS10 running on a 64-bit Win2008R2-SP1 Standard server. Currently we have approx 2000 hosts (clients and servers) in the policy hierarcy. The server is a virtual server (VMWare ESXi) with 6GB memory (2 GB dedicated, 4 GB thin provisioned) and 1 virtual CPU (3,2 GHz), and with VMWare tools installed. The disk is divided into three partition: System (20GB), F-Secure (20GB) and swap (6GB).

After migrating the PMS settings to the new server and having it run in production for a week, I noticed that it was running rather slow. I'm running the PMC directly on the server, not via the network, and the console appears to be lagging, almost to the not usable. A quick look at the Task Manager reveals that it is Java that is using a lot of memory. The java.exe *32 process is taking between 50 and 100% of the CPU at any given time. A reboot does not solve the problem.

Is this normal? Do you have any tricks up your sleeve that you can help me reduce the resources java.exe uses?

Thanks in advance for any help.

Find more posts tagged with

Comments

MJ-perComp

Great.

with PM10 there are now certificate that need to be installed locally and it even brings "Accounts" with different Passwords and multi-User. So there should not be any lagging any more.

Have fun!

Popeye

Thank you. I added one more CPU, and the server is running smooth as silk now. Smiley Very Happy

The reason for running the PMC on the server itself is that the previous versions of the PMC were lagging over the network. Running it on the server itself removed the lagging. PMC on the server also removed the need to distribute certificates to the admins, who always seemed to have a reinstalled computer with no certs on it when they needed access the most... Smiley Mad

MJ-perComp

Hi,

with 2000 hosts the machine is nicely equipped with ressources, but 1 CPU is simply TOO few. please increase to at least 2 and increase polling intervals for AUA and policy/status to at least 30 Mins.

There is no need to run the console on the same machine, so move that to one of your PCs.