[Galaxy S Advance I9070 General] mkaluza:
I'll take a look at those optimizations, but looking from looking at https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html it seems that-Os is -O2 without just a few flags. But I'll look for this ArchiDroid stuff :)

The other thing is that while system partition can be expadned without big problems, you still need to read data from it, which takes time for I/O and RAM to store it, both of which can be scarse. I've felt noticeable increase in apps startup time after switching to ART (still love it though) and I've even started to consider striping /cache partition over both internal flash and sdcard to increase bandwidth. And of course there's the memory, which isn't exactly made of rubber, and I think there still are new devices comming out (India?) that have only 512M of ram...

What wonders me though is that I observe less memory pressure on art then on davik despite the cache being 2.5 times in size.

Yes, without Dalvik Android probably wouldn't be here right now

Actually it wasn't Google - they bought Android and AFAIK Davik was part of that design already.

I wouldn't be so sure... Back at my uni times I made a desperate try to write something for Symbian and failed miserably... While I'm not a big fan of java (mostly because it's huge requrements and the corporate "just throw more hardware at it" approach - used to be a sysadmin), creating an Android app that works and does something useful is a snap, while that Symbian stuff was hell (It was like writting a windoze app using pure winapi, but one level lower... still having nightmares about it sometimes...). And where's Symbian now? So the creating a possibility for almost anyone (Google's App Inventor) with an idea to write/create an app is something you can't pass by - it opens the environment for new people with abilities they already have,and that's always a good thing. You don't even need to use java to write apps... There are JavaScript environments with nice GUIs, there's SL4A and probably much more...

---------- Post added at 02:27 PM ---------- Previous post was at 02:06 PM ----------

I wasn't referring to the idea of swap itself there (which is a separate discussion, esp if you want to place it on flash...), but to where it was being turned on - It was in a place where Average Joe couldn't do much about it (yes, you can add an init.d script to turn it off, but how many times will you explain this to people?). Placing it in init.d, or better yet - offering a script they can put in /data/boot.d if _they_ want would make it much easier/possible to modify.

It should. And about /preload... whose idea was it to format it "just because" upon system flash?! :) man I was pissed when after flashing some rom I found my lvm trashed;P That was a really bad idea... ;P The good thing is I had only /cache on LVM then...

Yeah ;) hack the planet! :)

That's the discussion about itself I was talking about. From my experience with swap I found it to be useless at most, harmful at worse (I'm talking zram here - using a swap partition from internal flash is as bad of an idea as humanly possible). The only useful way of implementing swap I see is per app. And I don't mean that "this app can be swapped and that cannot", but that "if this app is the foreground app, then turn the swap on, and when that app quits (as in quit and close, not switch), slowly swap everything in and deactivate swap". But since I don't feel like arguing about something I don't care, I build my kernel with and without swap support to satisfy all (download stats are 2/3-noswp, 1/6-swp, and 1/6-debug, the last one being a mystery to me ;P)

P.S.

It's nice to meet someone using proper sentences here... I was starting to forget what's it like ;P you must be old :P