the test scenario is the analysis of a big monolithic app.

I built a technical reproducer application consisting of 10k packages, each with 10 classes. the classes itself just contain a main method with a sysout.
This scenario is derived from a real world application which is even bigger, but the number of packages and average of classes is representative.

loading the analysis configuration page for the first time takes some time, due to determining the available packages. since it's 10k, i wouldn't expect it to load immediately.

however a few observations:

• loading the analysis config page again, though the app list hasn't changed, takes again quite a long time
• it seems that the package selection check mark wasn't rendered / not yet rendered after those ~ 10seconds.
• the CPU consumption is significantly high, resulting in an unresponsive page or, sometimes with chrome, a process I even have to kill.
• loading the analysis result page takes also quite some time.