Performance Improvement

[sboisvert]

Add deferRender = true to improve the performance in older browsers by only creating the DOM nodes for the items that are currently being displayed on page 1.

See https://datatables.net/reference/option/deferRender

[timarney]

Works great. For this PR thinking we should only include the patch for the single file change in tables.js

[obrien-j]

rebase to get rid of already merged commit plz

Can you also profile this on a datastore of say 2000 records, to get an idea of improvement in load time plz.

[timarney]

Tested with a sandbox database 3314 records.

Using BrowserStack + Sandbox DB to localhost so not super accurate but seems like for IE 11 this speeds things up by guessing around 8secs.

The big thing in this case is it's not creating a bunch of DOM nodes that it doesn't need off the top.

As an example to help illustrate this, if you load a data set with 10,000 rows, but a paging display length of only 10 records, rather than create all 10,000 rows, when deferred rendering is enabled, DataTables will create only 10.

[obrien-j]

@ptd-tbs @sayaHub We might want to cherry pick this into existing production deployment.

[timarney]

@sboisvert

The K8s branch was merged #127 so you can rebase to master then make you one line update.

if (!options.deferRender) options.deferRender = true;

[timarney]

Closing in favour of #129

-> same fix