Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
well i am new to linux and h/w so i could be completely wrong sorry to mods if i posted the topic in wrong section
ok what is happening is my ram is getting full by cache ( which is normal i am aware of it ) but when my ram is kind of full the data get transferred to swap ( while 90% of my ram is used by cache ) after a while ( take around 6-10 hrs ) both cache and swap is full resulting in poor performance . In one rare case performance drop as bad as 100+ load . Now is it normal for linux to use swap even if ram is free??
how can i check if this is not hardware fault ( i.e ram ) . note this is a live server so i can't even think to use memtest86+ which require me to reboot the system .
I can see nothing wrong with that picture at that time, the kernel just has swapped out 110MB stale memory, which I wouldn't worry about after 17h uptime. Does it get more overtime? It would be helpful to see a sequence of free outputs over time, maybe you set up a cronjob to log the memory usage every two hours, so that we can see a trend.
Distribution: K/Ubuntu 10.04/12.04, Scientific Linux 6.3, Android-x86, Maemo
It's normal for a Linux system to run with the RAM fully utilized. But, if you feel the desktop is unresponsive, & you want the system to swap less, you can adjust swappiness...
At a terminal run;
It'll probably return 60, meaning 60% likelihood of swapping, generally.
To change it temporarily (to 5% likely to swap, in this instance);
sudo sysctl vm.swappiness=5
To change it permanently;
sudo gedit /etc/sysctl.conf
sudo kate /etc/sysctl.conf
sudo nano /etc/sysctl.conf
... and either modify or add the line
(again, for 5% likelihood of using swap)
Also, If you are using KDE (especially on a version older than 4.8), one source of system slowdown can be nepomuk/syringi/akonadi server running,... Attempting to index all your files for social media connections.
You can deactivate nepomuk and stringi easily by going to the KDE settings utility and look for (and run) the search the search function as well as session settings, and look for nepomuk, and deactivate them (and in the session settings, to stop the service and also deselect it from loading).
Some applications will use swap even if you don't want it to and some will not even clear it.
Your issue still seems to be a bad driver or bad program that is taking up space. Normal use should remain constant and not raise with time. Guess it could be some user issue logging on and never off or such but that has been mostly fixed long ago I'd think.