-
Notifications
You must be signed in to change notification settings - Fork 45
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
Check performance of libjpeg-turbo in a dockerized setup #150
Comments
@mo3rfan The request hitting geoserver can be a fixed WMS GetMap request in the jpeg format. Please provide here the outcome of the tests along with the test setup. |
It does feel like the build without libjpeg-turbo is slightly faster on my M1 macos. I ran the
I also had to run the ab tool many times over on the same test setup to get results that are 'more stable'. Without libjpeg-turbo
With libjpeg-turbo
|
Ok, there is no point in keeping libjpeg-turbo in the dockerfile then. Removing it will improve the build time of the docker images and get a lower footprint in terms of image size. Thanks @mo3rfan |
In the dockerfile we are downloading and building the libjpeg-turbo native libraries from source with the goal of getting better performance on jpeg compression.
It is not clear though with recent JVM versions what the benefit is in terms of performance. We want to run a quick benchmark and evaluate if it is still worth building and installing the native libraries in the docker image.
The text was updated successfully, but these errors were encountered: