Created attachment 38042 Using JMeter for performance tests and reports, we have seen serious performance degradation introduced as of 2.4.47. We use apache as ingress into our K8S clusters. Upon upgrading Apache from 2.4.46 to any higher version (we tried 47, 48, and 49) we see massive failure rates in JMeter reports for our performance tests. See compressed & attached web archives. If we need to configure something to turn something off that was introduced as of 47 it is not clea in release notes or change logs for 47 that performance/performance testing would/could be affected so.
You attachment is a Safari WebArchive and not usable for non-Safari users.
In order to investigate further we would also need: 1. The httpd configuration used for the load test. 2. Information about your load test, e.g. URL's, frequency, number of parallel requests, protocols used (TLS (which version), HTTP/2, etc). 3. Any changes in 3rd party libraries e.g. OpenSSL between 2.4.46 and 2.4.4[789], 4. Logfiles preferably at a debug or trace level. 5. Access logs which log the request times in ms (%{ms}T) 6. More details of the noticed performance degradation, e.g. lower amount of request throughput, slower answer times, etc.
There are long HTML lists of some performance figures on their test suites. Does not tell me anything really. I mean you see that things are slower, but one as no idea what they do.
(In reply to Rainer Jung from comment #1) > You attachment is a Safari WebArchive and not usable for non-Safari users. Then download safari
(In reply to Judea from comment #4) > Then download safari Then fix it for you..
(In reply to Yann Ylavic from comment #5) > (In reply to Judea from comment #4) > > Then download safari > > Then fix it for you.. sAfArI cAnNoT dO
So it seems that you need help somehow, please provide the requested informations.
(In reply to Ruediger Pluem from comment #2) > In order to investigate further we would also need: > > 1. Coming soon, needs redaction > 2. Coming soon, needs redaction > 3. There are no changes other than changing the https image from 46 to 47+ > 4. Coming soon, needs redaction > 5. Thats in the JMeter reports > 6. Thats also in the JMeter reports
(In reply to Stefan Eissing from comment #3) > There are long HTML lists of some performance figures on their test suites. > Does not tell me anything really. I mean you see that things are slower, but > one as no idea what they do. "We need performance figures" "The performance figures don't tell us anything" How bout that as of 47 there is a severe performance regression? Thats something.
(In reply to Yann Ylavic from comment #7) > So it seems that you need help somehow, please provide the requested > informations. Hence this ticket, and yes, will do
(In reply to Judea from comment #8) > (In reply to Ruediger Pluem from comment #2) > > In order to investigate further we would also need: > > > > 1. Coming soon, needs redaction > > 2. Coming soon, needs redaction > > 3. There are no changes other than changing the https image from 46 to 47+ What do you mean by image? A container image? > > 4. Coming soon, needs redaction > > 5. Thats in the JMeter reports Unfortunately it is not. I need the access logs with this information to correlate things. > > 6. Thats also in the JMeter reports I don't have Safari and I will not install it. Please provide it in a format readable for everyone (e.g. zip archive / tar.gz archive containing the reports).
(In reply to Ruediger Pluem from comment #11) > (In reply to Judea from comment #8) > > (In reply to Ruediger Pluem from comment #2) > > > In order to investigate further we would also need: > > > > > > 1. Coming soon, needs redaction > > > 2. Coming soon, needs redaction > > > 3. There are no changes other than changing the https image from 46 to 47+ > > What do you mean by image? A container image? > > > > 4. Coming soon, needs redaction > > > 5. Thats in the JMeter reports > > Unfortunately it is not. I need the access logs with this information to > correlate things. > > > > 6. Thats also in the JMeter reports > > I don't have Safari and I will not install it. Please provide it in a format > readable for everyone (e.g. zip archive / tar.gz archive containing the > reports). Forget it, we're going to switch to nginx
Apologies for the back and forth with my associate. May we kindly ask that the attachment be deleted on this ticket?
Done.