big game makes sphere tracker not very usable

[beauxq]

I opened the sphere_tracker page from the webhost with a not-really-that-big async (28000 locations) -
Lots of "web page not responding" trying to use it.

I tried putting a drawCallback ( https://datatables.net/reference/option/drawCallback ) in the configuration of the DataTable in trackerCommon.js to hide the table when the (filtered) number of rows is big, but that didn't really help much. A lot of the processing is in the filtering on every keyup event.

I'm not sure of the best way to handle it.
I don't know if there's a good way to do the filtering on the server or client depending on the number of locations.

Software

Website

[black-sliver]

Datatables dies at ~5000 rows, primarily because of the styles it applies. The solution is pagination, either client side (single json) or server side should work for the amount of rows we normally have.

Not really an expert, so I'd prefer someone else to implement it.

Edit: i believe there were two modes even when operating on DOM, but I didn't have success improving performance in another project and switched to json.

[ShinyNT]

I still think sphere tracker showing only progression by default would make it much more usable for big multiworlds (conveniently because it won't need to load literally every item, which is ultimately what causes the page to die)