Thanks for trying to address my question. I have read all the references you suggested, that is how I have been able to test its performance. as I understand it, the answer is: study all the Framwork code and figure it out yourself.
more to consider: The Binder suggestion better illustrates my concerns and need for further documentation of design and insight. Binder/AIDL -> serializable->CORBA-like->(lo, fd, stream, pipe, shmem... who knows) = painfully slow; remotable objects = security issues ContentProvider->SQLite = not so painfully but still slow I have measured a linear and sequential data access at 60-80 ms cross partitions for each of 10 applications (<~800ms) (I went up to 500 clones with interesting results) It seems like cross partition IPC is impacted by an empirical 20 ms event timer and also impacted by appplications being started and stopped. All this is guesswork in lieu of studying ALL of the code in the android Framework. Even when using only three independant applications it takes >100ms for the simplest of ContentProvider access. This is all done on baseline Android builds using the N1 The emulator of course is much much slower but that is understandable. Does anyone have a good reference that discusses tradeoffs, insights, design etc? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
