Performance issues in CA Web Viewer 12.1 for CA View database of PDF reports
Article ID: 139789
Updated On:
Products
Output Management Web Viewer
Issue/Introduction
Performance issues in CA Output Management Web Viewer for users accessing a CA View database of PDF reports.
Environment
Release : 12.1
Component : CA Distributed Repository Access System (CA DRAS)
CA View
CA Output Management Web Viewer
Cause
Unfiltered searches search the entire database
Resolution
The resolution for this case is to create searches with filters to avoid unnecessary use of resources
Any date range greater than 10 days can cause a search Of the entire database.
The search is stopped when we buffer enough reports to present to the user in the sysout selection list. If the clients report is not on the selection list and the user Hits PF8, the search resumes, until possibly the bottom of Reports.
So, a date range larger than 10 days AND a low number of date matches (less than selection screen) will search entire database then present them to you on the selection list.
OR a date range larger than 10 days and many date matches (enough to fill the selection screen) then the selection list gets presented and the search stops (Not complete). When user hits PF8, the search resumes until we buffer enough matches to present the selection list again or end of list.
In either scenario, the I/O and CPU time will be very close due to search of the entire database.
Any date range greater than 10 days can cause a search Of the entire database.
The search is stopped when we buffer enough reports to present to the user in the sysout selection list. If the clients report is not on the selection list and the user Hits PF8, the search resumes, until possibly the bottom of Reports.
So, a date range larger than 10 days AND a low number of date matches (less than selection screen) will search entire database then present them to you on the selection list.
OR a date range larger than 10 days and many date matches (enough to fill the selection screen) then the selection list gets presented and the search stops (Not complete). When user hits PF8, the search resumes until we buffer enough matches to present the selection list again or end of list.
In either scenario, the I/O and CPU time will be very close due to search of the entire database.
Feedback
Yes
No
Powered by
