8

Last night I looked at an Android app.
Going to put it bluntly, I don't like java much.

But Android takes it to a whole new level.
I was talking to our (SlimRoms) framework dev about how the database transactions used to take 400ms, and it was cut down to 10ms by, changing to xml with some kind of a reflector (so xml would be saved in the background).
This is atrocious. As a web developer, I live in a world where you can do thousands of transactions in that time (albeit on faster hardware).

So how is it that all of the abstractions in Android add up to a single read/insertion in Android (and I'm talking about an app written by Google) takes 400ms?

Every time I go in that channel to talk to them, I find something screwed up. Gah.

Comments
  • 0
    Something is wrong in your code, 400 ms should happen if you have 10.000+ records.
  • 0
    @modislaszlo, those timings were from the Android settings app
  • 0
    So what I'm hearing is don't bother with SlimRoms, keep it Cyanogen (now Lineage) or AOSP...

    And yeah, 400ms is way too long unless you're doing server calls.
  • 1
    @Neotelos, the timings are from AOSP. SlimRoms is working on optimisations on top of what Google has done, and introducing our own framework
Add Comment