Interesting. I assume that otherwise this host is the same (OS/CPU etc.) as
others where it runs without probs? We are not ghosted by some strange
blabla-lake hyper threading thingie singularity?
Need to think about this.
> Am 23.11.2017 um 13:43 schrieb Stefan Priebe - Profihost AG
>
Happy Turkey everyone!
Just added backport proposals and patches for mod_md to 2.4.x/STATUS. The
mod_ssl patch proposed is the minimal one, without policy or other niceties.
I hope I did get all Windows related changes, people might want to check this.
Also, I think I just got the basics from
Hey,
could you try the patch below and produce such a lovely log file again?
H2MaxWorkers please back to before, unconfigured. Thanks! This is a small
change that a) logs the interaction with h2_workers a bit more and makes sure
that time gets lost where I think it does. It also switches the
*argh*, i was too fast no it did NOT fix the problem. It even happens with:
H2MaxWorkers4096
Sorry about that.
Stefan
Am 23.11.2017 um 13:42 schrieb Stefan Priebe - Profihost AG:
> Hello,,
>
> setting:
> H2MaxWorkers1024
>
> fixes the issue for me. The main problem is how to i know
Hi,
Am 23.11.2017 um 14:10 schrieb Stefan Eissing:
> Interesting. I assume that otherwise this host is the same (OS/CPU etc.) as
> others where it runs without probs?
Yes and no i got some more reports by colleagues where they've disabled
http2 as the customers had unexpected long loading times.
Hello,,
setting:
H2MaxWorkers1024
fixes the issue for me. The main problem is how to i know how many
workers are needed? How can i detect whether all workers of h2 are busy?
Stefan
Am 22.11.2017 um 13:23 schrieb Stefan Priebe - Profihost AG:
> Hell Stefan,
>
> will send a log to you in a
