We're current facing performance issue of PEGA8 applications.

Though performance tools, we can find that such issue often starts from a gen_xxxxxapplicationdata.js request.

Full request URL like:

https://hostname/prweb/IAC/s6z5yZ_AcLWppACxZyTSqQ%28%28*/!MTKBPMApp/webwb/gen_240a86b382f44cd735dc401150550f3d_applicationdata_0.js?sysgen=1

When the issue happens, from the Chrome console, we can find that this request often takes more than 10s.

But from the access log of our application server, it shows the request took only 0.003s to complete.

And also, we found follow dozens of JS/CSS requests also take more than 10s; but these requests are load files from disk cache instead of remote application server. One of followed requests like:

https://hostname/prweb/IAC/s6z5yZ_AcLWppACxZyTSqQ%28%28*/!MTKBPMApp/webwb/pzpega_ui_harnesscontext_1966789930!pzevalharnessjson_11925044216.js!pzpega_ui_lib_provider_1192545302!pega_yui_11739265364!desktopwrapper_13357940816!pzautomationscripts_1782369863!pzpega_ui_jquery_11914439343!pega_ui_harness_14169033283!pzpega_ui_animation_11917519552!pzpega_ui_harness_actions_11416648922!pzpega_ui_crc32_1193200667!pzpega_web_mashup_11901594283!!.js

We want to know the relation ship between gen_xxxxxapplicationdata.js and other JS file requests.

Are requests like pzpega_ui_harnesscontext_xxx.js waiting for gen_xxxxxapplicationdata.js to complete? Or actually these request should be initialized at the same time?

Thanks very much.