I have around 1200 Hosts in my PolicyManager - and the Admin console opens in less that 20sec (time from clicking the icon and including password entry and selecting the desired policymanager) ...
i think, there is something wrong with your installation if it takes 5-10min to open ...
Seems like a disk issue. Memory and CPU utilization is pretty low on the server, but disk queue length while loading is around three.
I have ~2000 clients connected.
Just clocked it, and it took 6mins for admin console to open after enterin password.
Any idea, if pmc is capable of using multiple CPUs?
just checked it now ...
20sec from click on icon to Logon Windows
12sec from password until console is open
Policymanager is on an Windows 2012 R2 VM on our VMware farm.
VM has 2 vCPUs and 4GB ram
Disc Queue around 0.2 while loading
in Total over 1200 systems including our branch offices worldwide
Our PMS runs on Debian Linux 8.5 32-bit, running in an ESXi 5.1 VM. CPU usage is fairly constant at 14% average, across two virtual cores (the physical CPUs are Xeon E5530 2.4 GHz). Disk usage is fairly close to zero at all times, but opening PMC caused the disc read rate to rise to 900 kb/sec for a few seconds; this did not occur when I closed and re-opened it, suggesting that everything it needed was cached in RAM. Memory consumed is at 3 GB flat (the allocation for that virtual server), but active memory is 256 MB on average.
Looking at Process Explorer on my own PC, the CPU usage graphs suggest that most of the delay is on the client PC. On my PC, PMC tends to load so fast that I can't get reliable CPU usage information. javaw.exe creates a lot of threads, far more than there are CPU cores, and during loading there are plenty of active threads. As such, the loading process does appear to be able to make pretty good usage of your CPU cores. I/O figures (general, network and disc) are all very low, suggesting that CPU is the only constraint for PMC on my PC.
thanks for changing the colors and layout in Policy Manager 12.20
Now it is really readable and better to use.
Thanks for listening to the customers!
I'm not sure that anyone is actually testing this interface. If you have a top taskbar, and you maximise the window, it maximises to the correct size, but vertically offset by the height of the taskbar. This is a new bug created in 12.20.
I don't know why the developers are going as far as they can out of their way to not just use a native window. Is Java really such an abomination that you can't have a native title bar on a window, and a native maximise behaviour? I would have thought that a native frame would be the one single thing that you'd be guaranteed from a Java framework (with native title bar, window shadow, and maximise).
This topic has been closed due to inactivity. If you would like to discuss this topic further, please start a new post.
You can reference this topic in your post by adding this link: