On 10/12/10 21:49, ssrk wrote:
Hi Auke, harri
Thanks for the reply.
As mentioned in Auke's reply
I doubt 128mb will provide a pleasant experience...
I am actually trying on a device with 128 MB ram, UX is up on it but it almost
uses the entire 128MB memory even without any application being launched.
when I see the memory usage using 'top' command, the below is what I get
(sorted based on mem usage)
VIRT RES SHR %MEM
260 meego 20 0 127m 23m 15m S 0.3 20.7 0:25.68 sysuid
261 meego 25 5 108m 19m 12m S 0.0 17.8 0:27.23 duihome
258 meego 20 0 82136 17m 9.9m S 0.0 15.4 0:10.80 meego-im-uiserv
240 root 20 0 24312 15m 348 S 0.0 14.0 0:05.70 Xorg
253 meego 20 0 49708 11m 9904 S 0.0 10.3 0:04.75 mcompositor
285 meego 20 0 22068 4080 228 S 0.0 3.6 0:04.10 tracker-store
256 meego 20 0 29992 3680 364 S 0.0 3.2 0:05.11 mthemedaemon
257 meego 20 0 59452 1988 472 S 0.0 1.7 0:03.00 mdecorator
345 root 20 0 2212 1040 848 R 1.6 0.9 0:00.63 top
322 root 20 0 4864 900 636 S 0.0 0.8 0:00.28 bash
262 meego 39 19 18700 860 408 S 0.0 0.8 0:01.92 tracker-miner-f
216 root 20 0 3672 764 192 S 0.0 0.7 0:00.15 login
215 meego 20 0 5236 720 52 S 0.0 0.6 0:00.27 uxlaunch
309 meego 20 0 25884 604 196 S 0.0 0.5 0:00.70 tumblerd
250 meego 20 0 6284 420 188 S 0.0 0.4 0:00.64 gconfd-2
247 meego 20 0 2820 376 36 S 0.0 0.3 0:01.13 dbus-daemon
159 root 20 0 5956 348 32 S 0.0 0.3 0:00.00 sshd
why are those top 5 process taking this much of memory?
Several reasons. I made the above table myself last week as well to look
into footprint issues and see roughly the same numbers. However, it's
not trivial to understand what is going on...
sysuid loads a bunch of plugins and thus is more than just one
component. In reality, there can be several dozen of plugins active
within sysuid.
duihome also performs several functions and gets accounted for by the
graphics stack for pixmaps etc., so the memory used by this application
doesn't reflect the size of the binary.
as for meego-im-uiserv, I haven't figured out yet where the memory goes.
All of these should be put on a diet, for sure.
so 128MB RAM is not good enough to run meego?
That depends, we're not explicitly excluding devices from the list of
supported devices only if they have 128mb or less. Linux is able to run
on a surprising low amount of memory, and some devices are able to run
very well under these conditions due to the hardware design.
I also don't think there's an official stance on the amount of memory
required to ""run MeeGo"". In general, with 512mb most devices see a lot
better performance than with 128mb, so you can draw your conclusions on
whether it's 'good enough' for everyone or just 'good enough' for *you*.
Auke
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
