Trying to free up ram (SOLVED)!

[cURIOUSgEORGE]

 I just tried to move some tce's to On-Demand too save more ram...........

I had everything in On-Boot with control panel system stats telling me that I have 192000kb of free ram

soo, I move about 5 items to On-Demand and rebooted then immediately checked system stats free ram and see that it says 5000kb left of free ram..........

How does that even make any sense! ?

And on TOP OF ALL OF THAT "I THEN MOVED EVERYTHING BACK TOO HOW IT ORIGINALLY WAS (On-Boot) AND NOW IT SAYS I HAVE 35000KB of free ram!

Haha, whoaaaaaaaa, what's going on here? Am I missing something ?

Educate me, Thanks George

[cURIOUSgEORGE]

 Read this and as confused as I am

Comon now, bring out the big guns........

Curaga

TinyPoodle

Gerald Clark

Or anybody else that has a clue........

Thanks, George

[tinypoodle]

Do

Code: [Select]

sudo cache-clearbefore measuring free mem.

[cURIOUSgEORGE]

 TinyPoodle YOU SCARE THE SHIT OUT OF ME (You know too much) hahaha

Thank you VERY much, that worked!

I wonder why it didn't work just by simply shutting down and rebooting.

Anyways, I'm happy, soo thank you.

[cURIOUSgEORGE]

 Okay, like I said that did work but................

 Now, after I reboot I'm noticing that everything is ****** up again,hmmmm
It's still seeing the "incorrect" amount of (MemFree and Committed_AS)

Do I have to run the command (sudo cache-clear) every time that I want to see accurate results? Or is there another solution ?

and also when I do run (sudo cache-clear) ------> Why doesn't it change the (committed_AS) ?


Thanks, George

[gerald_clark]

The system will use all available memory as cache, releasing it as needed.
Either run cache-clear before running 'free' or add up the free and cache values.

[cURIOUSgEORGE]

 Hmmmmmmmmmmm, "That's some mickey mouse shit right there."

 As much as I love TC/MC more then anything, it just doesn't seem proper - to have to do that.

hmmm

[gerald_clark]

You don't "have" to do anything.
Just ignore the memory figures and run your applications.
This is not a Tiny Core issue.  All Linux work this way.

[cURIOUSgEORGE]

 Gerald, I know that I don't "have" too but, if I want to see accurate results then I "have" too.

You are right though, just ignore it because I know the truth is that I have more available ram then it's actually showing, and ignoring it is what  I will do..... "no biggie" , just sucks a little bit but it is what it is and thanks for your help once again.

[tinypoodle]

and also when I do run (sudo cache-clear) ------> Why doesn't it change the (committed_AS) ?

Where exactly is that?

[cURIOUSgEORGE]

From the control Panel and then click on system stats then click MEM.

[tinypoodle]

Found same in meanwhile with

Code: [Select]

cat /proc/meminfo
Not sure of what relevance it would be though.  

[tinypoodle]

The system will use all available memory as cache, releasing it as needed.
Either run cache-clear before running 'free' or add up the free and cache values.

Running cache-clear would not exclude non-droppable cache as opposed to subtracting.
I am under the impression that the part of tmpfs which resides in RAM is accounted as cache, which is not unsignificant with TC in particular.

[Rich]

Hi cURIOUSgEORGE
I've seen the subject of concern over free memory come up a couple of times before. One of the
design philosophies of the memory manager is that "unused memory is wasted memory". As a result,
when you closed a program it stays in memory so that it will start quicker if you decide to run it again.
Now when you start a program that requires more memory than is free, the memory manager looks
through the memory for sections that are not part of running programs and starts freeing up the oldest
pieces of memory for the program you are starting. This is a simplistic explanation but it gives you the
basic idea. So unless you are having problems, a low number for free RAM means the memory
manager is doing it's job. I've also seen it suggested to run cache-clear periodically in the background
to boost the reported amount of free memory, this is a bad idea. To demonstrate, the program I am
currently working on takes 2 seconds to compile. After running cache-clear it takes 10 seconds to
compile, and if I compile it again it's back to 2 seconds. It runs faster because the memory manager
is keeping the most recently used data in RAM. When you are done reading this would you please go
to your first post, click on edit, and change the title to something relating to the subject, for example,
"Trying to free up RAM" or "Why do I have so little free RAM" or something else appropriate.

[vinnie]

thanks for clarity, hiro, this is interesting