Hi,
ext ssrk wrote:
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
Above values are fairly useless. Please use something that reports PSS
and Swap usage (from SMAPS), for example:
http://www.selenic.com/smem/
Some examples of using above are here:
http://elinux.org/Using_smem_on_Android
Maemo has also SMAPS data based tools, for example this:
http://maemo.gitorious.org/maemo-tools/sp-memusage
(There's some documentation for maemo-tools in Fremantle SDK docs, but
that's somewhat out of date for the latest tools versions in git repo:
http://wiki.maemo.org/Documentation/devtools/maemo5
)
Or if you want more detailed information, use something based on
kernel pagemap information, like this:
http://git.itanic.dy.fi/?p=scan-pagemap;a=summary
(I have no idea whether above are already packaged for MeeGo.)
why are those top 5 process taking this much of memory?
I think it would be more appropriate to ask about this on
the meego-touch-dev list.
All MeegoTouch apps have currently:
1. GL command buffer and some other things required for GL operations
(SGX driver requires this to be locked in RAM, it doesn't work
with swapped out memory)
-> currently 6MB minimum[1]
2. C++ overhead from Qt & MeegoTouch classes (vtables, typeinfos etc)
-> 0.5MB minimum if app isn't using a startup mechanism
that can share this[2]
3. CSS style handling
-> earlier well over 1MB, currently >0.5MB[3]
-> which MTF version you're using?
4. Qt shader compilation results
-> 0.3MB minimum[3]
5. Lots of other smaller things (font handling, locale handling,
socket buffers etc)
[1] can be tweaked down from /etc/powervr.ini globally, or per
process from the process specific SGX config files, if you're
_sure_ that the app(s) will never use more (SGX doesn't handle
running out of it very gracefully).
If app is idle on background, it's possible to drop
the GL context and associated resources. This is being
looked into for MTF system processes, for normal apps it
could be done automatically.
-> Which version of MTF you're using?
[2] applauncher that's used to speed up app startup can also do this,
but it (version you're using) might still require some fixes.
[3] These will also hopefully go down more.
so 128MB RAM is not good enough to run meego?
No. Even if you get it up, running e.g. Browser in the "remaining"
memory would be hopeless, today's web pages require hundred(s) of
MBs of RAM to to work properly (coupled with Browser/JS/Flash overhead).
It would spend all of its time swapping. Without well working Browser,
the internet experience goes down the drains...
- Eero
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
