Long start up time on the community solid server

[thhck]

Initiating component loading
and
Loaded component
steps takes quite a while when starting the community solid server.

Is there room from improvement here? What could be done speed up startup time?

[rubensworks]

How long does it take for you exactly?

Pinging @joachimvh here as well.

[rubensworks]

Config precompilation could be an option, but that would make swapping config files less flexible.

[thhck]

If I change just one line in CSS, re-build and re-run , I feel that the build time is not that much, but the starting time will take a while. Does CSS has to re-parse all the config files ? Shouldn't that only happen if config files are edited ?

[joachimvh]

Starting the server is not impacted by when the latest build was as all config files need to be read.

I did just realize that the CSS boot time is going to be a bit slower since internally it calls components.js twice. Once to determine which CLI parameters are supported and should be converted to components.js variables, and then a second time with the new bindings for those variables.

[thhck]

Starting the server is not impacted by when the latest build was as all config files need to be read.

Yes, that what I'm questioning: can we avoid this componentjs loading time when we don't touch the config file ( therefore, they should be no need to parse them again )
But if I understand well, the config precompilation could solve this issue.
Also, I just though maybe I can npm run build without stoping and restarting the server ? I will give it a try.

[joachimvh]

Due to the way CSS works standard precompilation will not work I think as it uses two components.js steps. A specific precompilation for CSS might be needed.