This message was deleted.

Hi. One needs to profile what happens, but the default image is definitely not designed for millisecond-range response times. Switching to non-docker App might be required

switching to non-docker App

you mean standalone jar or building my app from scrach with lirary? What kind of Jetty tuning you mean? in-code adjusting, or jar parameters?

switching to non-docker App

you mean standalone jar or building my app from scrach with lirary?

Standalone JAR should be enough

What kind of Jetty tuning you mean? in-code adjusting, or jar parameters?

Hopefully JAR parameters will be enough. Again, hard to say without profiling

what if I build my own docker image around a standalone ? will that help?

Hard to say without profiling (c) 🙂

Thanks for answer, I ll definetely try this out!

But really, it depends on so many factors that one cannot say. There are so many possible perfromance tweaks possible. You have to keep in mind that the Docker Engine is not great when it comes to networking delays. You may get to 10ms with Docker, but maybe using another container runtime is a first step if it does not fit