Maintaining UI responsiveness when processing large query
Good day Support,
Hope you are well.
We have a question from a client that we would like some insight on.
Below is the use-case.
"Their issue is that the Yellowfin front-end becomes unresponsive when a report with a large number of rows is requested.
In their case the only way to recover the system is to restart the Yellowfin server.
Closer investigation revealed that they are indeed requesting a very large number of rows between 2m - 6m and hitting the maximum cpu processing limit allocated to the server.
We have showed them ways to limit the number of rows returned including Yellowfin's own row limiting ability.
Is there a way Yellowfin can detect this type situation let's say as a result of a poorly designed report and either auto terminate the query or govern the worker threads in such a way that it the system as a whole remain responsive?"