@josevalim I found the possible culprit. We use quantum to have cron-like scheduling in the app. By using the time command on the dev env I noticed similar startup times of around 5~6 seconds. The setup of quantum uses a genserver as a worker in the main Application file, and I noticed some issues on the board over there regarding timeouts. Removing the worker there brings the test startup down to <1 second!
I will head over to the issue board over there and for now only add the worker to the supervisor when not in test. For the actual application the timeout is not too bad, we only need to start that once.
