What is the best practice to use Kendo UI grid with "long run" server side data source? I have a web page with two tabs. The grid in on second page. The data downloaded on login process and average time is about 20-30 seconds, that's not good. If I create remote data source then opening the second tab is taking 20 seconds to display the grid content.If I choose the first tab and then return the second tab then the grid takes 20 seconds again.
The amount of records in the data source is 0-5. The problem is that SQL code has to check too many things (and controller accessing another web site) and cannot be optimized.
Should I go with web workers? In this case the data could be downloaded when the first tab is displaying. Or might be exist another solution? Or something already in grid functionality that I have missed? What is the best practice for such case?