today we finally switched from Ti 1.3 with iOS 3.1 to Ti 1.4 with iOS 4.0.1. Surprisingly, the transition was absolutely hassle-free (!!!) and we could directly re-use the complete code. Super!
We recognized a negative behaviour: the generating of a small tableview (15 elements, 3 labels and 1 imageview per row) now takes 2.4s instead of <0.8s. A tableview with 50 elements takes now 3.4s instead of 2.2s seconds to load. That’s not much, but it is annoying and noticable to the user. Did you change anything in how tableviews are processed?
I mean, are there new tricks to optimize code for a fast tableview drawing with Ti 1.4?
P.S.: the tests were done on a 3G with a stop watch (to leave the code untouched) and yes, className & setData is used.
I see the same (slow table views):
Unfortunately now answer yet. Maybe you can confirm that the code in the above links is very slow for you either.
Yes, I see that your code is far slower on Ti 1.4. We will now downgrade to Ti 1.3 because that Tableview-performance issue is really a drag on the user experience. I don’t understand why there is such a strong performance issue since most Titanium API methods are really well performing implemented?!
Fellows at Titanium, will 1.5 bring an improvement to tableview performance? I mean, it doesn’t need to be the fantastic native speed done in Objective C, but maybe something less than second for a medium-sized tableview?
By the way: the issue in Ti 1.4 seems to be in the tableview’s .setData()-method.