Hi Jesse, > I've filed an internal issue for us to investigate our serialization > performance problems.
That would be great. The slow serialization really is a problem. Not only for me, but for many others, too. The advantage of serialization simply is that it is the most simple way of writing and reading data. Of course there are disadvantages like update inconsistency. But still there are use cases where these do not occur, like with static data or cached data that is deleteted on every update anyway. > How are you parsing the CSV? Are you buffering the input? Any > mechanism that generates many intermediate Strings will be inefficient > on a device. During my first test I used String.split(), which generates intermediate Strings. So my solution was not as optimal as possible, yet by means slower than reading all data from a SQLite database. > > 4. Reading in the data using serialization is slow. The funny thing > > here is: It takes a bit longer than loading the XML file. > > This is unfortunate, but not too unreasonable. Depending on what > parser you use, XML might need to do as much work as serialization - > reflectively inspecting types and doing proper serialization lifecycle > requires a lot of complex code. I suspect there are still many > opportunities to improve Java serialization here (caching reflected > fields?); I'll investigate. I would be very happy if the serialization (and unserialization) gets faster in the future. I know this is not easy, but many applications will profit from this. Thanks & regards Marc Reichelt || http://www.marcreichelt.de/ -- 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
