Inserting UITableViewCell rows in begin/endUpdates block performance issue
| Originator: | bryanhenry | ||
| Number: | rdar://7316174 | Date Originated: | 12-Aug-2009 02:39 AM |
| Status: | Open | Resolved: | |
| Product: | iPhone SDK | Product Version: | 3.0 |
| Classification: | Performance | Reproducible: | Always |
Summary: Attempting to insert rows in a -beginUpdates/-endUpdates block using -insertRowsAtIndexPaths:withRowAnimation: causes the UITableView's dataSource to be asked for cells for all inserted rows. This leads to a major performance hit while the dataSource object is creating the asked for cells in -tableView:cellForRowAtIndexPath. The performance is especially terrible when compared to something much less efficient, like -reloadData.
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!
Radar number
Are you sure that this radar number is correct? I just submitted one and got 7201596, which is about 115,000 less than yours (but maybe they are not allocated strictly linearly, and rather depending on which backend server you end up)