Bursting memory?

[itwasntme]

I gave the tweaks Roger and Scott suggested as they applied to my non-problem VPS. Of those they suggested, I was able to make the following changes:

• Turn off "Compress interface pages using gzip compression reducing bandwidth usage for cPanel and WHM".
• Disable all the stats programs.
• Turn off Spam Assassin.
• Turn off the IMAP server.

Before the tweaks, Free reported:
VPS memory usage:
Used: 423 MB
Total: 256 MB
Burstable to: 1024 MB

After the tweaks, Free reported:
VPS memory usage:
Used: 376 MB
Total: 256 MB
Burstable to: 1024 MB

After restarting the VPS, Free reported:
VPS memory usage:
Used: 312 MB
Total: 256 MB
Burstable to: 1024 MB

Don't know if I'll notice a difference, but it makes me feel like I did something!

Thanks for the suggestions, guys.

[DOCENTA]

Yes for a full featured cPanel 350 -400MB is normal. Mean MySQL , Spamassassin, postgresql, exim etc. Spamassassin is using a lot of memory if it is set to start with a big value for Maximum Children.

[Scott]

I am at 389 right now. So it is sticking to that amount. I don't know why SpamAssassin takes so much memory when it isn't even being used. That's horrible.

Itwasntme, after rebooting, you will notice the RAM moving up and up over a span of 12 hours as your MySQL gets used by your visitors. You can't go by the reboot until the day after to see what it really will stable out at. Seeing mine at 380-400, I am very happy.

DOCENTA, well, that is good to know, except for the fact that HICs smallest VPS is 256MB and burstable to 1GB. That means every customer they add to the server is bursting.

[roger]

Originally Posted by Scott

I have my VPS set to manual updates for cPanel upgrades so I just upgraded. Now I see the setting for max memory is 128.. so I switched mine to 129 as you suggested.

After the upgrading of cPanel and setting to 129, I am at 381. I just didn't like seeing it at 550 as before, that was horrible considering I am not on the Extreme plan.

FYI...

The 128 issue was also mentioned by the tech in one of my cPanel tickets. (When I was trying to set 128 after logging in later or rebooting, I would always find maxmem back at 256. It was a cPanel issue. Here is that message:

I have set the maxmem to 129. It is 128 and below that will not work.

I have tested this on a few test servers and I am getting the same result. It
appears the wording logic is not correct, as it will not take 128 so 128 or
less is not acceptable.

--
Cory McIntire
cPanel Technical Support
Level 1

[itwasntme]

Thanks for the info on the reboot, Scott.

Now ~24 hours out after reboot I'm getting:
VPS memory usage:
Used: 347 MB
Total: 256 MB
Burstable to: 1024 MB

Looks like it helped quite a bit. The server hasn't been that busy in the past 24 hours, though, so I am going to watch for some more climbing over the next few days.

[Scott]

It's sad because I just installed PHP/Apache/MySQL on my test environment and it only needs <50MB with no traffic (internal testing server). cPanel really hogs memory like no other!

[DOCENTA]

You can turn off the spamassassin via WHM's Tweak Settings (SpamAssassin Spam Filter) and then via Service Manager (spamd) so not to be restarted.

[Disku]

Thanks for the advices! Really helped out