Open talawahtech opened 4 years ago
Yes, it is a bug...
@stefanocasazza ok thanks for confirming. Are you able to provide a some insight as to what the issue is? Why is --enable-captive-portal
required and why does it affect the performance like that?
--enable-captive-portal indicate a limited context (for example POST is disabled), in general it is used only with specified usp and plugin (mod_nodog, mod_nocat)...
2020-05-24 15:56 GMT+02:00, Marc Richards notifications@github.com:
@stefanocasazza ok thanks for confirming. Are you able to provide a some insight as to what the issue is? Why is
--enable-captive-portal
required and why does it affect the performance like that?-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/stefanocasazza/ULib/issues/80#issuecomment-633234768
Hi,
I have been playing around with ULib after seeing how impressive the performance was on the Techempower benchmarks, and I was trying to see what the performance is like while using a more standard .usp file instead of the hyper-optimized version used in the Techempower tests. However when I try it using the same docker configuration used in the Techempower test, my simple .usp file does not work e.g.
Then I run curl against the endpoint this is the response that I get:
And the body is not returned. I looked at the code and played around with the feature flags until I realized which one was causing the problem. When
--enable-captive-portal
is used, simple .usp files no longer work, but the techempower optimized ones do. Is this a bug?This is the configure command that I used in my test:
When I remove
--enable-captive-portal
from the configure command, .usp files work again, but performance of the optimized json and plaintext examples drops by about 30%