Answering my own question in case someone else comes across this issue.
ab does indeed have this behavior. It starts the first connection and sends the
request. Only once the header of that first response has been received, the
other connections are initialized.
Here's the relevant piece of co
Hi everybody.
I have a question about the distribution of workers between processes
and threads.
Let's say that I have a 12 core machine and that I want to server up to
300 parallel requests.
I have the choice between, for instance, 10 processes with 30 threads or
30 processes with 10 threads
Hello!
I would advise the following:
- configure 'LogLevel md:trace2' to see all the details the module does until
you have analyzed it
- remove the "staging/foo+bar" folder with the failed attempt
- reload your server
mod_md will pick up that foo+bar needs renewal and you will see in the log
