Number of config files and performance

HA version: hass.io 0.63
Hardware: Raspberry Pi3

For a while now I have been splitting up my configuration into quite a few config files in several directories. In particular, I like the concept of packaging several different components related to the same task or automation into one config file.

Therefore, I would like to know if there is any impact on performance compared to just having few config files.

I have seen a recent degradation of performance, but in my book it shouldn’t be related to how the configuration code is organized - or is it a factor?

If I understand how it works correctly (and that’s a really big if), then it might slow down the initial start up time a fraction (but should be barely noticeable on most systems I guess), but shouldn’t affect general running.

I split mine a few weeks ago, seems that it may take a couple of seconds to assemble them on boot but once assembled it seems to run the same. Splitting really helps with knowing where and what to edit for a specific device or automation.

I also believe that the file are assemble on start, and that performance should remain the same after the initial start-up is completed.

I don’t know how much files you use but I have 5 main config, 8 customize, 11 group and 43 packages files, and I don’t have any performance problem :wink: