Build: NetBeans IDE 7.4 Beta (Build 201307092200)
VM: Java HotSpot(TM) Client VM, 23.25-b01, Java(TM) SE Runtime Environment, 1.7.0_25-b16
OS: Windows 7
leogtzr: Using the tag <jsp:scriptlet>, in general it's slow with scriptlets.
GUEST: was just running a simple Hello World example
johnjullion: enabling java ee
jyeary: Startup and creating a new project.
Maximum slowness yet reported was 17161 ms, average is 10044
Created attachment 138211 [details]
Adding Petr Hejl to have a look at this too.
In GF plugin there is instance provider being initialized and it's reading configuration from disk. Slow piece of code is retrieving some class path information for maven:
This can be removed from library initialization code and it can be done as lazy initialization with first maven dependencies request.
It will save approx. 1/2 of time. Another part is server instances loading (18% of time) but I would like to keep it there.
Pater, do you have an idea if this can be started as asynchronous task in infrastructure?
I do see readInstanceFromFile is calling writeInstanceToFile (which takes time). Does it make sense?
As I suggested in some other issue in case you don't need OptionalDeploymentManagerFactory.finishServerInitialization use the Proxy (learn by example in other server plugins).
That sounds bit weird to me but yes, you are right. This should be fixed. But it's 1/10 of total AWT queue delay. I'll have a look at proxy after all P2s will be handled.
*** Bug 241207 has been marked as a duplicate of this bug. ***
This should postpone the initialization of libraries to a time when it is really needed - web-main caf64576a7f1.
Integrated into 'main-silver', will be available in build *201505140001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Petr Hejl <email@example.com>
Log: #233869 - org.netbeans.modules.glassfish.javaee.Hk2JavaEEPlatformFactory.getJ2eePlatformImpl: LowPerformance took 8596 ms.