PPM Support Tip: Page loading issue on staffing profile page in PPM 9.2x
Some users are experiencing a performance issue when rendering the staffing profile page, when having a high amount of positions.
On Staffing Profiles page , if end user wants to use weekly view, system will generate one cell for every week for one position.
For instance, if we have 113 positions, the total number of these cells will be 113*52*3 (suppose the time period is 3 years) =17628.
It is a big table and for Internet Explorer it costs the system resource to render the big table.
In 9.22, we introduced Jquery DataTables (a third party plug in) to PPM and it relies on performance of browser’s engine.
If you click F12 on IE8 and turn on “profile” function, you will find most times spent on Jquery/Datatables related operations.
These operations like DOM cost more than 60% of JS execution time.
For instance, if we open a SP in 9 seconds, the total JS execution time is around 6 seconds but JS execution time of Jquery/Datatables is around 5 seconds and we cannot modify Jquery/Datatables’ code directly.
In terms of performance tuning, we have reached the limit in tweaking PPM code.
Since the bottleneck is performance of old browser’s engine, we have following suggestions:
a) Deploy 922-TROUBLESHOOTING-QCIM1L54579-V1.jar.
RnD created a patch reduces the number of positions that can be display on staffing page.
The performance will be improved by nearly 40%-50%.
According to testing result, if we had 120 positions, the "load time" of weekly view was around 18 seconds.
After deploying this patch, the "load time" of weekly view was 9 seconds in IE8.
b) Try to use new versions of browsers like IE10, IE 11, Firefox 32 and Google Chrome.
These browsers use new engines and the performance of staffing profile will be improved.
c) Try to use "Monthly view" instead of "Weekly view".
If customer want to assign 8 hours for every week, they can assign 32(4*8) hours to a month.
d) In 9.30, we introduce new UI with a better performance in Staffing profile