Currently we spend anywhere between 100 to 150 ms (3-4%) to detect if any module in modules/ has changed or not. In a real(production) environment, this may not be necessary, since in such an environment, a change in the installation is done via an admin tool like pkg or admin console. If admin module can enhance their tool to notify glassfish launcher about any change made in the system, then we should be able to avoid this logic in production environment. Prioritize as you see fit. Close if this can't be done.