Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-2063] Android: Table view performance degraded > 2X in 1.5.0 (when measured by way of this test case)

GitHub Issuen/a
TypeBug
PriorityMedium
StatusClosed
ResolutionFixed
Resolution Date2011-04-17T01:57:58.000+0000
Affected Version/sn/a
Fix Version/sRelease 1.5.0
ComponentsAndroid
Labelsandroid, android_refactor, performance, regression, tableview
ReporterThomas Huelbert
AssigneeDon Thorp
Created2011-04-15T03:09:22.000+0000
Updated2011-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

Comments

  1. Marshall Culpepper 2011-04-15

    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

  2. Marshall Culpepper 2011-04-15

    (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...

  3. Marshall Culpepper 2011-04-15

    Marking as fixed, the problem here was the inaccurate reporting of the test

  4. Thomas Huelbert 2011-04-15

    Titanium SDK version: 1.5.0 (12/03/10 09:29 33c2058), closing as resolved, sorry bout the false negative there.

JSON Source