Question
S & P Global Inc
US
Last activity: 28 Feb 2019 12:57 EST
How to measure browser screen rendering time?
As the data on screen increases(amount of data and number of sections) the performance of system deteriorates in IE 11, however the Chrome is very fast and responsive irrespective of data.
The AES/PAL/Profiler readings does not capture the browser screen rendering time, Is there any tools within or outside PEGA to capture performance numbers/Screen rendering time?
Accepted Solution
Pegasystems Inc.
IT
An increase in memory usage is expected when new tasks are performed and there is nothing to worry about as long as browser memory reduces after such tasks are terminated. If you should observe a steadily increase in the browser memory usage timeline that doesn't reduce even after closing the previously opened tasks you may be in front of a browser memory leak.
In such case please try to reproduce the issue using the sample application installed with the Platform or the Strategic Application in use.
If the issue is not reproducible then check any customization applied to UI rules (js, html sections, etc...) in your Application and ensure that javascript best practices are applied (callbacks are properly unregistered, global variables are used wisely, DOM references are released after usage, etc..) otherwise please create a Support Request and supply a detailed description of the issue.
Thank you,
Domenico
Pegasystems Inc.
IN
Adding to Rachit's comment ,
In the network tab ,The DOm ContentLoadedtime & Load time shows you the complete load time for the screen.
Pegasystems Inc.
IT
If Chrome is way faster than IE you may want to check the memory usage in IE to determine if the slowness is caused by memory pressure.
You can check IE memory usage in Task Manager or by using the F12 Developer Tools Memory Tab.
Then you can start a profiling session and take consecutive snapshots to check if memory usage increase excessively.
Please note that overall browser performance is also affected by the memory available on the system. The OS may start swapping to cope with memory pressure caused by programs and this will have a noticeable affect on browser responsiveness.
Accepted Solution
Pegasystems Inc.
IT
An increase in memory usage is expected when new tasks are performed and there is nothing to worry about as long as browser memory reduces after such tasks are terminated. If you should observe a steadily increase in the browser memory usage timeline that doesn't reduce even after closing the previously opened tasks you may be in front of a browser memory leak.
In such case please try to reproduce the issue using the sample application installed with the Platform or the Strategic Application in use.
If the issue is not reproducible then check any customization applied to UI rules (js, html sections, etc...) in your Application and ensure that javascript best practices are applied (callbacks are properly unregistered, global variables are used wisely, DOM references are released after usage, etc..) otherwise please create a Support Request and supply a detailed description of the issue.
Thank you,
Domenico