4 ms·
Funny how similar this is to just a simple filesystem.
by randyrand 11y ago
Funny how similar this is to just a simple filesystem.
- azinman2 11y agoThat actually makes me wonder if storing things as such might be a great way to go.... like just reading 58283/photo.jpg or 58283/name.txt or whatever... of course you have you then pay the price on decoding whatever you get from the network into these files. JSON parsing is a major problem on Android. When I also first ran into the 35ms parsing I thought for sure I was doing something wrong. Nope.. the latest phones can get down to 4-5ms JIT'd but still iOS is an order of magnitude or two faster which completely changes your architecture decisions. Why this can't be integrated in to be fast & native I've never understood. It should have landed in Android a long time ago.
- TwoBit 11y agoIf Facebook really cares about performance so much, I wonder why they don't just implement that app engine native.
- azinman2 11y agoA bit surprising but I'm guessing it's the multi-architecture fat binary problem they don't want to solve? Until recently debugging native plus Java was very difficult, and most of the UI stuff is in Java not native. As far as I'm aware Dropbox uses c++ between iOS and android shared for all the model/network bits so other biggies do it.
- deanCommie 11y agoI'm curious (knowing next to nothing about iOS development) - what makes iOS orders of magnitude faster at JSON parsing?
- azinman2 11y agoSeems to be native versus JVM. My guess is it's a combo of string processing, many temp objects, etc with too many interpreted versus JIT'd code paths.