VMS 2.3 on Solaris - Slow config generation - Java Issues?

[ntrngrusr]

Any idea why generating a simple configuration for a single sensor takes more than 1 full minute? The whole process to make a sensor config change is slow at best yet the server is showing 1.2 GB free mem, procs are running very low, yet this process is slow.

Maybe I am just getting frustrated but I really feel this needs to be a faster process. I know about the generate and deploy button at the top but I am surprised at how slow this can be as well. Is Java a root cause of this because in other apps I have had the issue with Java.

[#2]

To avoid unnecessarily slow response times while using VMS, you install VMS security configuration management components (Firewall MC, Router MC, IPS MC, and AUS) on a separate server from VMS monitoring components (Performance Monitor and Security Monitor).

[ntrngrusr]

I have that exact config actually. One server running IDS MC and the other running Sec Mon. Still it is a very slow beast. I really see Java as the main killer here, at least the way it is coded.

It still works, it is just very slow which is not good during an event that requires fast actions. In that case I move to the sensors directly and then I have to reimport the sensors after my changes are complete. Not ideal but it gets the job done.

[npham]

Hi,

From my experiences with various Java applications, Java performance on Sun SPARC is slow in comparison to Intel based platforms.

I would recommend you try deploying your VMS 2.3 installation of IPS MC on a Windows Intel platform and see for yourself.

Added bonus, you might find this Java benchmark useful reading material.

http://www.volano.com/report/index.html