Wherever you deploy the SNMPCollector, other robots should not be on that same hub. That adds many objects to the NISCACHE directory and slows everything down drastically.
You should learn how to use the Alarm_Enrichment to modify alarm messages with Origins, Source names, etc.
The QoS_Processor probe is practically useless. we use a simple SQL Update script that sets the Origin, Nim_origin, and Modifier in its place. That way you only have to run the script one time, not 24/7 like the QoS_Processor requires.
CA does a terrible job pointing things like this out...
We run the SNMPC on a physical system, 32Gb ram over 1500 profiles with no major issues.
CA does not consider taking 15 minutes to load the SNMPCollector Admin console as a Major issue, nor do they think that making one change requires it to reload again. You are out of luck if you need to make multiple changes. We have learned to modify the templates rather than deal with the Admin console. There are other tricks to setting it up and using it that CA hides...