Hogging memory like no tomorrow!!!

First off, WordPress isn’t hogging your memory.

From your minimalist paste, it doesn’t look like anything is wrong. Linux normally takes up all available RAM for disk cache, buffers, etc.

Since you aren’t really swapping, it looks like you’ve got plenty of RAM.

In other words, I don’t see anything wrong. Are you having any specific trouble?

Adsense deluxe runs everytime a page is loaded, and I think jeromes keywords does too. Statcounter will for sure run evertime a page is loaded. How else to count stats?

see: this

Clark, not pulling anythign from Adsense deluxe in this situation.. as far as statcounter all it does is embed the counter in the footer… stupid plugin … regardless it makes things more organized but should only embed it into the code once and that’s it.. If it runs every time I woudl be suprised…

Error, I have to disagree WordPress is hogging the memory.. Let me explain. First of all I didn’t realize inactive memory was memory that would be freed up when needed so that helps the way the last one was shown. Here is another one after I clicked around in the wordpress backend about 20 times to different sections.. It gobbled up another 600 megs of memory as I had it down to roughly 700 megs active, just from clicking around..

Here was the readout after doing that

ast pid: 12553; load averages: 0.18, 0.13, 0.05 up 1+04:15:59 16:28:49
208 processes: 1 running, 203 sleeping, 4 zombie
CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle
Mem: 1316M Active, 355M Inact, 190M Wired, 74M Cache, 112M Buf, 4344K Free
Swap: 3901M Total, 16K Used, 3901M Free

Here is the readout after waiting a few minutes so the ram it is tying up should of been freed back up … but it isn’t

last pid: 12576; load averages: 0.01, 0.07, 0.04 up 1+04:18:20 16:31:10
203 processes: 1 running, 198 sleeping, 4 zombie
CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle
Mem: 1315M Active, 355M Inact, 190M Wired, 74M Cache, 112M Buf, 5572K Free
Swap: 3901M Total, 16K Used, 3901M Free

Basically every time I click anything in the wordpress backend I use about 20 megs of memory and it isn’t ever releasing it. So right now if I click 20 more times in the backend it will raise to using 1900M and I’ll be flat out of memory.

Best way to put my problem, is it’s as if whatever I do in the backend doesn’t ever quit using the ram until I manually kill the PIDs off .. if that makes sense?

Did you read the link about how Linux manages memory that I provided?

Anyway, it still isn’t WordPress using the memory; it’s MySQL and apache.

Come back when it starts going more into swap. Until then, there doesn’t appear to be a problem.

Ahh O.K. No I didn’t catch the linked article error – That helps explain alot… Can you tell me though … I can’t use free – m on my box so all I can get my readins off of is top, this is the most recent reading

Mem: 1467M Active, 202M Inact, 191M Wired, 76M Cache, 112M Buf, 3732K Free
Swap: 3901M Total, 16K Used, 3901M Free

I get now that the 1467M are active meaning they are being used to put pages in the cache essentially (what isn’t actually being used anyways) and I have another 202 megs that are inactive at this point I could still pull from.

How, if I can’t use the free -m command can I tell how much memory the box is actually using that isn’t in swap mode? Does the active memory ever reset itself ? Thanks for answeering a linux newbie’s questions and being patient! I actually was dropping my mysql db on the old server which is why I was so frieked about this when I saw it … especially after paying to upgrade it ??

You’re probably overpaying for capacity, even, unless you expect your blogs to get a whole lot bigger.

The information shown in top is the same as that you would get from free -m, so that much doesn’t really matter.

It’s true you have about 200 megs free, and as long as you really don’t go into swap, you’re fine.

I’m running several sites, which get thousands of hits daily, on a tiny VPS with 160MB of RAM. It doesn’t even go into swap. So you could probably do with a lot less than you have.

Thanks, the old box might have had issues due to the processor I am guessing then since it was somewhere around 600 mhz with a gig of ram and it was killing mysql. The only other thing I can think of is it was the processor speed on the old box causing the problems?

and yes these sites are getting very little traffic atm – it is time I start pounding them and take advantage of what I am paying for here… ??

Yeah, for 600MHz you need to tweak MySQL a bit.

error: you’re a hero!
rml704: Start writing! After all it’s a blog and content is king ??