Investigate if Actions are the cause of long compilcation times

[jwoertink]

For our app we compile the main app binary, and a separate mosquito worker binary. Both binaries require the same app code with the exception that the worker binary doesn't require any actions.

This is the difference in compilation time

I think to further investigate this, we just need to benchmark compiling an app, then compiling a separate app that doesn't use Actions, and see if there's truly a difference, or is it that we're doing something with our app?

My app has 28 action classes... Though it's a decent size, that's not really that many.

[jwoertink]

toddsundsted/ktistec@9acf0c3

This is an interesting find. According to this comment, it's possible that blocks could be a source here. I'm not sure if this helps us here or not, but it's worth adding to the investigation.

[jwoertink]

Working on some app updates, we've added 257 new actions to our app, and the compilation time is roughly the exact same... So now the question is, why does our worker code build SO much faster if it's not the actions causing the increased compilation time?