Note that there are some explanatory texts on larger screens.

plurals
  1. POFast managing of tables with ~10k rows in Javascript
    primarykey
    data
    text
    <p>I've been working with tables and a huge amount of data. There are a tables in my website with 10 thousand rows. This table has dynamic search, filters, etc. I've been using pure JavaScript considering performance, but it gets laggy with this amount of rows.</p> <p>Do you guys know any alternative for pure JavaScript with better performance?</p> <p>EDIT> I REALLY need to load the 10 thousand rows at once. I can load them all in the browser in 5 seconds. The main problems are the filters and search... </p> <p>EDIT2> The search is dynamic. I can search by name and filter it by first character. I've been working on it for months...</p> <p>SEARCH:</p> <ol> <li>search when the field has more than 3 characters and only when its length and characters has changed (onchange event on input may trigger multiple times when a character changes, so I make sure it only triggers once using some verifications)</li> <li>each row that matches the searched string is coppied to another table. The original table is hidden and the new one is displayed.</li> <li>when the user changes the search field or cancel the dynamic search, the new table is erased.</li> <li>Conclusion: it's faster to create a new table with desired elements than hide the undesired ones.</li> </ol> <p>FITLER</p> <ol> <li>The rows are actually in 25 tables (A to Z + non-alphabetical characters)</li> <li>When you select a character, only that table is shown</li> <li>Conclusion: it's faster to hide a whole table than hide the undesired rows</li> </ol> <p>Thanks for the repplies. I've edited with some extra info so we can narrow the possible solutions...</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload