I really thought all was well, I mean on boot up I was using around 60mb of memory
and after everything opened up it hung around 200 or so. BUT soon as I do something such as emerge -s, it goes to crap instantly consuming 200+mb of memory (from 60, so between 260-300) and of course that depends on just how long it took it to search. It just keeps going like this, never reducing. I didn't sweat it much. Two nights in a row however, the next morning waking up... with nothing running mind you. Shut everything down except fluxbox.. it used up almost every bit of my 1gig of memory over night. I tested this again by rebooting, and not opening anything, and then checking the following morning to the same results. Using slabtop I can see xfs vnode and inode both using 200-300mb of memory. I could be off base on how important this is or isn't. If its not I'll just forget about it, I think in conky I can actually remove the disk buffer cache or whatever its called from the memory output on the graph. However this seems really ridiculous even if xfs was THAT bad with its cache, that it would consume nearly 1 gig of memory over night.I am more inclined to believe it might related to something else, but it may just be that kde sucks, and so does xfs. If thats the case it looks like a format and retry round-3, before I try switching down to a 32bit version of the os...
