On Wednesday 24 March 2010, fpp wrote: > True also, but only on N900/Maemo5. On the N8x0/Maemo4 platform, > where the gecko-based Micro-B is very slow and kludgy, Tear is a > real screamer, fast and slick. It is only less "usable and as well > productized" because it is a one-man effort in POC state. Clearly > there is no reason it could not be as good or better than the Nokia > browser if it was granted the same level of resources...
Some unscientific experiences of Tear and MicroB... Tear on N8x0 is faster than MicroB on N900 for tasks like browsing the maemo forums, and N900 has something like twice the CPu speed :) However, after browsing for a while tear becomes slower and slower and slower, with most of the time spent in IOWAIT with a fairly low rate of data actually transfered to mmc (50-100kbyte/s), if I don't restart it, eventually this ends up in several minutes long lockups spent 99-100% in IOWAIT with about 10-50kbyte/s traffic to mmc (it really hates random writes) MicroB's swap file use is nicer, it seems to bite a huge chunk of ram and do something with it that makes the OS sequentially push out large chunks to swap, achieving rates of 1-2megs/sec with only a few secs of UI hang. Then it changes its mind and releases the ram and you've suddenly got 20M free ram and "safe" for another few minutes.. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
