slow nginx and "cold starts"

PercyDwn

So I was observing two things, that probably are related:

slow nginx
starting my dev-stack takes quite long. Not the stack itself, but the systems stacks nginx module after starting my stack. In the past it didn't take that long. Restarting my Mac, rebulding the stack etc. did not help. Any idea how I could check what causes this? It takes around 60-90 seconds for the system's nginx module to get started.
"cold starts"
The first request after some time to my indigo hosted page takes really long and subsequent requests (within ~ 60 seconds) are really quick again. E.g. the first request takes around 10 s while the following (identical) requests only take 100 ms. I have the feeling this is connected to my nginx-problem.

Indigo

Wow, that's really odd. I've not experienced anything similar. What services are in the problematic stack? Do you have any config overrides?

Could you create a second stack with the same services and config and see if it has the same result? If it's the same, would you mind sending me the corresponding log files?

App logs are stored at ~/Library/Logs/com.marmaladesoul.Indigo
Helper logs are stored at /var/log/com.marmaladesoul.IndigoHelper/IndigoHelper.log

PercyDwn

Indigo
My stack uses the apache, php 8.1 and mysql 8 services. I created a second stack with identical settings, but still the same problem. The only overwrites I use are xdebug and upload related settings in php. I sent you a mail with more details and the log files.

While stopping/starting the stacks I regulary get the following three errors:

Indigo

The first two likely cause the third, so I'll focus on them; exit code 124 is a timeout error, meaning Indigo had to give up waiting for a process to start. The problem is how to identify what process 82,929 was (it's quit by the time you get the error), and then work out what might be causing it to time out.

I've just extended the error so that it lists the command that was running at that PID, so in the next release this should be more helpful.

Thanks for emailing through the logs — I'll get back to you via email.