-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate a throughput config with Autotune for TechEmpower results Round21 #28
Comments
Created a TFB image (kusumach/tfb-qrh:2.4.1.F) with Quarkus 2.4.1.F using the branch https://github.com/franz1981/FrameworkBenchmarks/tree/round21_2.4.1.Final to try some runs. When the load is run with hyperfoil-0.16/wrk, I see following errors. But with Quarkus version 1.13.2.Final no errors are observed.
|
Probably need to increase the configured I suggest to use https://github.com/franz1981/FrameworkBenchmarks/tree/round_21 in the last commit, that's getting rid of other errors and has applied the most recent patches, but beware: in order to make it works there are few JVM args that cannot be omitted ie |
As Franz said, the max number of connections have been opened, The default max is 100 iirc. If you have defined the upper bound on connection pool size to over 100, then this error is likely. But another question is, if the max bounds are the same as previous runs, why do we now need to open more than 100 connections to perform the test? |
Not sure It's like the previous one anymore, I remember Sanne changed them in https://github.com/franz1981/FrameworkBenchmarks/blob/3d273a8edfe9bb022784938f9286546cad42a226/frameworks/Java/quarkus/resteasy-hibernate/src/main/resources/application.properties#L13 |
Initial size of 512 would immediately cause the issue, if the pool is set to pre-fill |
The run which throwed the above error doesn't use any tunables. Makes sense why it did throw this error. Below are the quarkus tunables and their ranges which are in my list now. Do I need to increase the upper bound
Also, autotune tunables in this experiment will be Quarkus and JVM tunables. Will be keeping cpu and memory constant(requests and limits being set to 4c - 4GB). Is that okay ? |
The text was updated successfully, but these errors were encountered: