[TIMOB-2063] Android: Table view performance degraded > 2X in 1.5.0 (when measured by way of this test case)
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2011-04-17T01:57:58.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Release 1.5.0 |
Components | Android |
Labels | android, android_refactor, performance, regression, tableview |
Reporter | Thomas Huelbert |
Assignee | Don Thorp |
Created | 2011-04-15T03:09:22.000+0000 |
Updated | 2011-04-17T01:57:58.000+0000 |
Description
g1 running 1.6 and the sim running 2.2 Ti Mobile sdk 1.5.0.02c264.
1.BaseUI>Views>TableViews>Performance
results, on a G1 running 1.6: 1.4.1.1. = 6341ms, 0.08 ms per row; 1.5.0 = 2785ms, 0.18ms per row
Hey Thomas.. Correct me if I'm wrong, but the numbers you pasted don't seem to add up.
2785ms (1.5.0) is over twice as fast as 6341ms (1.4.1.1). It looks like the "per row" calculation is actually wrong. This test averages the time spent over 500 iterations, which means the 1.5.0 test should've yielded 5.57ms per row, and the 1.4.1.1 test should've yielded 12.682ms per row
FWIW, on my EVO I'm seeing 1031ms, 2.062ms per row
(from [eb5923af9d3dd2870499c9e16fb5b784877adebd]) divide duration by count to get the per row perf time [#2063] http://github.com/appcelerator/titanium_mobile/commit/eb5923af9d3dd2870499c9e16fb5b784877adebd"> http://github.com/appcelerator/titanium_mobile/commit/eb5923af9d3dd...
Marking as fixed, the problem here was the inaccurate reporting of the test
Titanium SDK version: 1.5.0 (12/03/10 09:29 33c2058), closing as resolved, sorry bout the false negative there.