[SOLVED] Conky has me like, why is my RAM always cached\full? So: [BLOGED]Clean RAM every 10 minutes...

jamison20000e · 12-17-2016, 06:08 PM

http://www.linuxquestions.org/questi...minutes-37249/ have fun!

Edit\add: Any other ideas welcomed?

syg00 · 12-17-2016, 06:35 PM

Very bad idea.
A rudimentary search should have found linuxatemyram - read it.

jamison20000e · 12-17-2016, 07:05 PM

LOL! I thought the same like... it knows what it's doing but still!

szboardstretcher · 12-17-2016, 08:55 PM

The holy trinity of memory information

Code:

free -m
vmstat
cat /proc/meminfo

Remember this:

free: memory that is currently used for any purpose;
shared: a concept that no longer exists. It's left in the output for backward compatibility (there are scripts that parse the output from free).
buffers: memory that is backed by files, and that can be written out to disk if needed;
cache: memory that is backed by files, and that can be reclaimed at any time (the difference with buffers is that buffers must be saved to disk before they're reused, whereas cache consists of things that can be reloaded from disk);
used -buffers/cache: memory used by applications (and not paged out to swap).

d_K · 12-18-2016, 08:39 AM

Does

Code:

no_buffers yes

exist in your conky config? I find if that line is "no", conky takes about ~15GB (yes you read that right) of ram usage (versus ~30MB normally.)

jamison20000e · 12-18-2016, 10:43 AM

Code:

no_buffers

is

Code:

no_buffers = false

here but does not have an issue...

I am however commenting out my edit to Crontab as it does slow down for example opening a large folder of thumbnails &c.

I can always run the script manually. With 8 gigs of RAM think full seems like a lot but it is a fresh install and have been working on it heavily so will see where it goes?

Thanks for the links everyone.

sundialsvcs · 12-18-2016, 11:23 AM

Like every modern operating system, Linux will try to intelligently use all of the RAM in your machine for some purpose or another. It does this primarily to avoid the need for disk I/O.

RAM is the only thing in the hardware of your machine that is capable of "keeping up with the CPU." Anything in RAM can be retrieved in a matter of nanoseconds, whereas anything in external storage will require milliseconds.

There are various "possible uses" for the RAM resource, the lowest-priority one being "buffers." (In other words, when there's a more-pressing need for RAM, the buffers will be the first to go ...) But Linux always wants to make intelligent use of all of the RAM resource that it has at its disposal, if there is anything at all to be done with it.

Let it alone. Let it do its job for you.

If you find that any particular application is using "far more than its share" of this shared resource, commands such as ulimit can be used to impose quotas upon it, so that it is not able to obtain more than its chosen allotment of anything. (And, you should do so.)

You should also, of course, adjust any configuration-files which this application provides, to control how much of these resources it knows that it should ask for. (Every industrial-strength application ought to have such a throttle, but not all of them do.) These are "soft" limits. The limits imposed by ulimit are "hard."

If any application uses vastly too much resources, such that (especially) "swapping" occurs far too often, the throughput of your system can grind to a halt in a syndrome known as thrashing. (Which is, shall we say, "not good.")

You need to prevent this by limiting both the mix of applications and the resource limits imposed upon each.

ondoho · 12-18-2016, 12:55 PM

https://www.linuxquestions.org/quest...minutes-37249/

ouch.

i sometimes run one of these commands to see how fast or slow some activity happens when it is performed the first time after boot, or later.
the differences are vast.

2 examples:
- logging into my desktop takes ~10s the first time, and ~2s subsequently. dropping the cache has it back to 10s again.
- https://bbs.archlinux.org/viewtopic....61072#p1661072 and onwards

in other words, you're deliberately making your system go uphill all the time.

jamison20000e · 12-18-2016, 06:10 PM

As long as I have everyones attention and we're on the topic of running head first in the wrong direction... I often sudo up a system task monitor while always having my partition set for "real-time priority" then give full priority to a process or more, that gets results!

Edit\add: it's general home* use laptop...

jamison20000e · 12-24-2016, 02:33 AM

This script still works grate. If I'm doing something heavy and my RAM thinks it knows what I want thus is %92 full from other #sh/ then my work gos slow until

Code:

bingo bongo baby

%16-RAM have fun!