4 Mar
2012
4 Mar
'12
1:03 p.m.
On Sun, 04 Mar 2012 11:10:48 +0100
Martin Gräßlin <mgraesslin(a)kde.org> wrote:
On Sunday 04 March 2012 02:36:51 Tiago Marques wrote:
http://www.linuxatemyram.com/
You cannot deduce from the amount of RAM used the amount of RAM
needed. This is extremely important for KDE based environments. KDE
has a very strong I/O usage at startup which results in an initial
high "RAM usage", but does not say anything about whether that amount
of RAM is actually needed or used. On my system currently only 280 MB
of RAM of my 8 GB of RAM are free.
Long story short: getting correct values for RAM usage on Linux is
non- trivial. I am not able to say how much RAM is really used, but
at least I know that it is non-trivial to get this numbers.
I already know that, that is why my numbers are from the +/-
buffers/cache line.
On Sat, Mar 3, 2012 at 10:49 AM, /dev/ammo42
<mickeytintincolle(a)yahoo.fr>wrote;wrote:
On Sat, 3
Mar 2012 02:36:00 +0000
Tiago Marques <tiagomnm(a)gmail.com> wrote:
Not my experience in ANY way. Not even with Nepomuk and other "bloat
disabled". Still, 200MB is a huge amount, you won't be able to run
almost anything else and you won't have 256MB available either,
so... tough. Raspberry Pi is the kind of device that can work
reasonably with
Trinity but not KDE4. Last time I checked I had Trinity running
in 80MB for RAM while KDE4 was having trouble fitting in 600MB.
For people who asked about reasons to keep KDE3 alive in
Trinity, I would point to a working testbed, if we ever get to
assemble one.
With a sane configuration KDE SC 4 is not heavy. On my 32-bit
Slackware 13.1, I had 200M used by the entire system. After
firing up KDE4 from another console with another user on another
X server, I had 340M used, still by the entire system. The
Raspberry Pi having a good GPU and 256M of RAM, I think KDE SC 4
can run without problem on it.