PEGACLSA_62V2 · Question #107
Consider the following situation: A PRPC application is running within a 1.2 GB JVM (Java Virtual Machine). There is approximatively 400 MB of free memory and garbage collector reclaims in average…
The correct answer is B. Reconsider the database table indexes by reviewing query plans. See the full explanation below for the reasoning.
Question
Consider the following situation:
A PRPC application is running within a 1.2 GB JVM (Java Virtual Machine). There is approximatively 400 MB of free memory and garbage collector reclaims in average 32 MB of memory in the course of an hour. The application is generating approximately 30 database alerts per minute. The database CPU runs at an average of 76% peaking periodically at 97%. The alert log file does not report any byte warning with a 10 MB threshold defined. The Rules Assembly count is 0 when a typical interaction executes in average 74.6 rules. The application CPU peaks periodically at 20% but otherwise runs in average around 12%. Users are complaining about poor performance. Their interactions take in average 4.15 seconds. Which of the following approaches is most appropriate to resolve this issue? (Choose One)
Options
- ALimit the number of database interactions by storing most data on a series of declare pages
- BReconsider the database table indexes by reviewing query plans
- CReduce the number of loop iterations executing on the large sets of data
- DAvoid retrieving the BLOB column during database interactions
- EReview the application profile log to determine which activities are taking the most time
How the community answered
(38 responses)- A5% (2)
- B82% (31)
- D11% (4)
- E3% (1)
Community Discussion
No community discussion yet for this question.