Mdk LE 2005 Eats ram?

Damnation · 07-15-2005, 02:55 PM

ok i maybe reading this wrong but i am finally using linux more and more infact aside from games i have been using mdk for everything i did on windows.

and i installed karamba today and it stats
Ram 997mb of 1011mb

now i think its saying its using 997mb ram i am like WHOA thats alot of ram to be using.
i don't understand why its eating so much ram
i am using Kde 3.3.2 i think
and metal spider theme.

a side note is any decent themes for that V of kde? i checked kde-look and they where average, and unfortunatly i do not hone the artistic skills to create my own.

i was told about fluxbox, i saw some screenies of a sweet looking desktop, emailed the owner and he informed me they where the standard fluxbox templates aside a background change

thanx for any information

regards Damnation

phantompgr · 07-15-2005, 03:03 PM

Does vmstat confirm the ram usage reported? (ie. run vmstat in a konsole - apologies if that is telling you to suck eggs)

ThePhantom

Damnation · 07-15-2005, 03:15 PM

Code:

procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in    cs us sy id wa
 0  0   2796  34436  57028 637492    0    0    59    77 1521  1100 27  4 67  1

i am guessing that saying i have 344mb free ram

ctkroeker · 07-15-2005, 03:41 PM

Quote:

Originally posted by Damnation

Code:

procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu---- r b swpd free buff cache si so bi bo in cs us sy id wa 0 0 2796 34436 57028 637492 0 0 59 77 1521 1100 27 4 67 1

Is that with karamba running?

Damnation · 07-15-2005, 03:44 PM

yup heres without:

Code:

procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in    cs us sy id wa
 0  0   3620  82848   5320 775048    0    0    71    97   83  1189 27  4 67  1

very big difference

phantompgr · 07-15-2005, 04:31 PM

Very small difference!

Difference between 34MB and 82MB of memory which considering you have about 800MB of active memory at the moment should not be a problem.
Try vmstat -a to compare how much active in comparison to inactive memory you may have.

The fact you have 700MB in the and probably some inactive should mean there is not a problem.

ThePhantom

Damnation · 07-15-2005, 04:52 PM

ah read the numbers wrong : oP heres vmstat -a

Code:

procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
 r  b   swpd   free  inact active   si   so    bi    bo   in    cs us sy id wa
 0  0   3620  15132 459624 517852    0    0    93   100  288   209 27  5 67  2

phantompgr · 07-15-2005, 05:39 PM

free inact active
15132 459624 517852

Yeah doesnt look as if you have any memory issues. Might need to read more on the subject but basically the cached memory and inactive memory is memory that has been used and still has old stuff in it (in case you wanted to reload an app etc..) but can be reclaimed by the o.s. for other use. So you basically have plenty inactive and cached memory if required. The free memory is apparantly stuff that is absolutely free so just not used yet. I dont think Karamber or MDK are having a problem. Lets face it I am running Fedora 3 here with 1.5 Gig of memory and httpd / tomcat / postfix / imapd / nfs / sshd / cups / vnc all running and these are my stats:

procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
r b swpd free buff cache si so bi bo in cs us sy id wa
2 0 0 39908 224412 576568 0 0 66 217 1135 1713 19 3 75 2

procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
r b swpd free inact active si so bi bo in cs us sy id wa
2 0 0 39692 459208 684708 0 0 66 217 1135 1713 19 3 75 2

Hope this helps.

Regards

Vgui · 07-15-2005, 08:02 PM

Another command to know for RAM checking is

Code:

free -m

Add the "free" and "cached" columns together, and that is how much RAM you truly have free. Linux caches the RAM as it is used, as compared to having to needlessly do this process each time. So the RAM is still available, but it is considered cached.

Damnation · 07-16-2005, 04:31 AM

ah thanx, didn't realise linux did that, been a windows user for so long,
that linux is a whole different concept, nice to see how it works tho,
seems to me that its more intelligent than windows ram and hd handling : o)