Large Data Draw Speed

[taitems]

The render speed on large sets is really slow. For some reason Chrome performance is roughly 3x worse than IE9 on my particular example (4,300ms vs. 1,500ms). It almost seems like it's rendering every row, but only showing the first X until you hit next page.

You might want to investigate how many repaints and reflows are being executed. DOM creation via strings might have to be the solution.

[taitems]

Just did a test with 500 items, 25 items per page.

Chrome came in at 103 seconds, IE9 at 47 seconds. Very strange.

[taitems]

On identical sets for another test, Firefox is clocking in at 3100ms and Chrome at 11000ms.

Interestingly, running profiles on the two shows an important difference.

Firefox spends most of its time (as expected) running the buildFragment jQuery function. The DOM construction and traversing should be expected to be the slowest and most costly.

Chrome instead spends the rest of its time running getComputedStyles.

No idea...

[taitems]

Landed a fix in my fork. Would be good if you could merge it into this fork.

Commit: 3f4acac

Results in 80% speed improvement on large sets in Chrome. There is a bug in either Chrome or jQuery where the jQuery hook for getComputedStyles runs incredibly slow. This removes the dependency upon jQuery for the getter, but leaves it for the setter.