CCM 4.1.2/Serviceability Reporter/CCMAdmin

[jerake75]

Anyone here using 4.1.2 yet in a production environment? We just pushed it out, and it's very stable..except for our publisher CCM. We have MSC-7835-1000 servers with 1 GB of memory, which I know is pretty low for 4.1.2, but 4.1.2 is officially supported on our servers.

In an effort to control the memory usage on our publisher, I am turning off every unnecessary service...and I was wondering if I would cause any adverse effects by turning off the Serviceability Reporter service. Has anyone done this?

Also, I've noticed that the CCMAdmin pages spike the CPU and memory whenever I open the pages...when I update Device Pools, the CPU pegs at 100% for a few minutes. Anyone else experience this behavior? Suggestions?

Thanks -

TMH

 

[pabb]

With current memory prices I would recommend to add 1GB;
totalling 2GB. My publisher (after working a half day with the administration pages) went to 1.6GB average and stayed there (until after reboot - went back below 1GB).

Regarding the CPU going to 100% might be related to java engine (am not sure); install 4.1.2 SR1? I remember a fix for excessive processor usage is included.

 

[jerake75]

Yeah, SR1 has that; I have ES16 installed, which includes SR1 plus more (fixed a problem with DCDirectory).

Actually, I convinced the powers that be to buy me new CCM servers...the new ones come shipped with 2 GB, so I can live with what I have until then, I suppose...memory usage is still incredibly high, though. I thought java.exe was the culprit too...

TMH