You are not logged in.

#1 2008-12-06 21:46:54

brando56894
Member
From: NYC
Registered: 2008-08-03
Posts: 681

Superkaramba and Cached Memory

I think I may have found the solution to my age old problem of the X server freezing when I have about 8 to 10 superkaramba themes open that monitor the stats of my computer. I figured it out before that cached memory is what is most likely causing the freeze, but would it be a good idea to set up a cron job that will flush the cache every hour or so?

here are three excerpts from the logs I set up for my memory (for the sake of cleanliness ill only include the first and last lines):

Dec 6 16:17:04 localhost mem/physical/application: 436588
...
Dec 6 16:41:14 localhost mem/physical/application: 518064
Dec 6 16:17:07 localhost mem/physical/buf: 19132
...
Dec 6 16:42:15 localhost mem/physical/buf: 19132
Dec 6 16:17:09 localhost mem/physical/cached: 807904
...
Dec 6 16:43:35 localhost mem/physical/cached: 814108

there currently is 1.3 GB out of my 2GB of ram in use and the only major programs that i have open (besides X) are amarok (which for some reason has a 500mb VMsize), firefox and superkaramba widgets. the freeze doesnt happen instantaneously but if its left alone for an hour or two it will freeze (only the mouse cursor will move) and ill have to crash X with ctrl-alt-backspace, and then everything is fine again.

Offline

#2 2008-12-07 14:23:30

brando56894
Member
From: NYC
Registered: 2008-08-03
Posts: 681

Re: Superkaramba and Cached Memory

i let it stay open overnight so it would freeze again and the buffered memory spiked around midnight, but i have no idea when it actually froze since i was gone by 5pm.

Dec 7 00:02:09 localhost mem/physical/buf: 19132
Dec 7 00:02:11 localhost mem/physical/buf: 21788
Dec 7 00:02:13 localhost mem/physical/buf: 24732
Dec 7 00:02:15 localhost mem/physical/buf: 28044
Dec 7 00:02:17 localhost mem/physical/buf: 32784
Dec 7 00:02:19 localhost mem/physical/buf: 36676
Dec 7 00:02:21 localhost mem/physical/buf: 38660
Dec 7 00:02:23 localhost mem/physical/buf: 40292
Dec 7 00:02:25 localhost mem/physical/buf: 41800
Dec 7 00:02:27 localhost mem/physical/buf: 45496
Dec 7 00:02:29 localhost mem/physical/buf: 49728
Dec 7 00:02:31 localhost mem/physical/buf: 50844
Dec 7 00:02:33 localhost mem/physical/buf: 51848
Dec 7 00:02:35 localhost mem/physical/buf: 52940
Dec 7 00:02:37 localhost mem/physical/buf: 54048
Dec 7 00:02:39 localhost mem/physical/buf: 55336
Dec 7 00:02:41 localhost mem/physical/buf: 56396
Dec 7 00:02:43 localhost mem/physical/buf: 57644
Dec 7 00:02:45 localhost mem/physical/buf: 58928
Dec 7 00:02:47 localhost mem/physical/buf: 60056
Dec 7 00:02:49 localhost mem/physical/buf: 61072
Dec 7 00:02:51 localhost mem/physical/buf: 62384
Dec 7 00:02:53 localhost mem/physical/buf: 63948
Dec 7 00:02:55 localhost mem/physical/buf: 70332
Dec 7 00:02:57 localhost mem/physical/buf: 75888
Dec 7 00:02:59 localhost mem/physical/buf: 82256
Dec 7 00:03:01 localhost mem/physical/buf: 82732
...
Dec 7 06:46:27 localhost mem/physical/buf: 78468

the app memory kept rising too theres way too much to post but it pretty much rose from 500mb to 1.3 gb from 5pm until 9am

Dec 7 09:05:48 localhost mem/physical/application: 1.13882e+06

Offline

Board footer

Powered by FluxBB