Open melezhik opened 1 year ago
The problem here I think is that a large data array is being transferred across the internet. The same delay can occurs when searching. I have found that the delay gets shorter as the data is cached.
There is a discussion about the search issue
A way of reducing the delay is also for the search / routine filter to be linked to a Websocket and for only some data to be sent out.
All this is possible in time.
The usefulness of the Routines page needs to be considered. There are lots of routines and all the data is transferred when the page is opened. A faster way of showing this data might be possible if there was a better idea about how this page could be made more useful.
It takes 1-2 seconds at the worst for the "filter by" control to refresh the routines table content when a user type something in (say, "sort"). Please see the screenshot. Tested in Mac OS (safari) and Chromium (windows)