Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed Colums on large datasets causing performance issues #34

Open
jlocashio opened this issue Feb 1, 2012 · 2 comments
Open

Fixed Colums on large datasets causing performance issues #34

jlocashio opened this issue Feb 1, 2012 · 2 comments

Comments

@jlocashio
Copy link

When attempting to load the plug-in on a large dataset (tested on ~1200 rows) with fixed columns (tested with 2 colums fixed), javascript is taking inordinately long to complete the process. FF9.0.1 gives repeated script warnings, and IE9 just waits, up to 2 minutes. If we remove the fixed columns, the render times drop to almost nothing.

The dataset tested has 1198 rows of 12 columns. The table is ajaxed onto the page (not that it should matter). I have also tried with a dataset of ~230 rows (same columns) which is also slower than it should be but not enough to stop the JS engine.

@pvannuff
Copy link

I have noticed the same issue.

Using the speed tracer extension of chrome, I boiled the problem down to the _fixHeightWithCss method. This method seems to be called on each cell, causing a layout event every time.

I could fix the performance problem a good deal by simply commenting out the code of that method, since our table does not require the height to be changed/dynamic.
First there were 384 layout events (taking 6 seconds), by commenting out the code only 28 layout events remained (taking 808 msec).

Some more information about this issue can be found on http://gent.ilcore.com/2011/03/how-not-to-trigger-layout-in-webkit.html and http://www.phpied.com/rendering-repaint-reflowrelayout-restyle/ .

I'm not sure how easy the code of this plugin can be improved to address this problem, but perhaps this information can help other people.

@neesonqk
Copy link

neesonqk commented Nov 7, 2016

Same problem here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants