Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Assessing the effect of data page processing on performance

Updated on April 6, 2022

To assess the effect (in your own requestor session) of data page processing on performance, access the Performance Analyzer tool and review the Full Details display. This page includes three elapsed times statistics, three counts, and three CPU time statistics.

For example, if there is a delay when loading the weather data in a mobile weather application, use the Performance Analyzer to review the amount of time the system takes to load the D_GetWeatherData page.

For more information, see Viewing data pages with the Tracer tool.

Note: There might be references to declarative pages in the Performance Analyzer tool. Declarative pages and data pages are the same.

  • Elapsed time spent finding data page names
  • Elapsed time spent loading data pages
  • Elapsed time spent determining if a page name is declarative
  • Declarative Page load activities executed (count)
  • Shared Declarative pages (count)
  • Shared Clipboard Size (bytes)
  • CPU time spent finding data page names
  • CPU time spent loading data pages
  • CPU time spent determining if a page name is declarative
Note: All times are in seconds. CPU times are available only on Windows-based servers.

You can also use Pega Predictive Diagnostic Cloud™ alerts to review performance statistics of your data page. For more information, see List of events and notifications in PDC.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us