Brian Stansberry wrote:
Even if the entire server start gets redone and MSC-21 results in batching being eliminated, the idea of tracking when all deployers instead of when all subsystems are available, and then allowing deployments to proceed as soon as the deployers are done makes sense.
Hmm, yeah not sure how this will look like - in the end the different batch basically just has the purpose of identifying deployers.
Brian Stansberry wrote:
How much start time improvement did this allow? What was your config -- web container plus a ROOT.war?
The configuration was basically what's in standalone plus the web container and a ROOT.war. The startup time was something around 1250ms (plus something) before and 950 (plus something) after separating deployers and services. Where the startup time without deployment is around 850ms. However those are really wall clock timings...
Brian Stansberry wrote:
I don't like the cast to ModelServiceActivatorContext. If we use this approach the param the subsystem activation API exposes should be ModelServiceActivatorContext (a better name would be good).
All this stuff (existing code included) needs a lot of javadoc; I had to think way too hard to understand what was going on!
Yeah, sorry - i fully agree. I did that in quickly and did not want to change too much before discussing the general idea.