search

CARLI / web-reports

Web Reports Web Based Reporting Tool
2 stars 0 forks source link

Two Elink reports returning a very large number of rows - concerns with system resource usage and UI usability #111

Open patrickzurek opened 8 years ago

patrickzurek commented 8 years ago

Two new reports were moved to production but were removed after it was noticed that they take a relatively long time to view the results for, and to download the CSV file for.

Quoted from issue #109:

Description of a Library's Collection -> General -> elink_bibs.report Description of a Library's Collection -> General -> elink_mfhds.report

When I run those reports for DPU they generate a huge amount of output (~70MB csv file). Loading a result for viewing takes a relatively long while. I hazard its long enough that the user might think there's something wrong and try clicking the result link again to re-open it which will cause everything to start processing and downloading over again, especially if they're accustomed to the normally speedy loading times of other results.

Paging works better, but it's still a little sluggish. Downloading CSV takes a little bit of time too before the file is ready to be saved and the download to begin.

It also causes significant CPU to be used for the duration of when the report is loading: screen shot 2016-10-19 at 11 11 20 am but since it's unlikely that many other users will be viewing the results for this same report at the same time I'm not as concerned.

So what can we do? Add a note to the report template page that loading the results for this particular report may take longer than normal?

Also, do we need to consider the load impact these reports might have on the production oracle server?

@gibsonjc suggested that they be removed from production until the implications can be further discussed:

These concerns your raised that these may pose problems for CPU, server load, and/or page loading times are serious, so I think we should remove them from production for now and let's discuss these things and do more testing on devel. No one is expecting these two reports to be there, so let's not tempt fate until we understand all of the issues better.

gibsonjc commented 8 years ago

At our meeting on 10/24, we decided:

For now, we’ll leave them on devel only and Chris can experiment with limiting or other ways to reduce the danger of using them. In future, Jessica will add “test report against UIU” to her QA procedures to watch out for reports like this that may tax system resources.