Obviously it would help to learn what CPU is doing. Does the application
become unstuck and start working normally after initial spike of activity?
I have not experienced exactly the same behaviour, and I have relatively
similar technology - a Tapestry application running inside Docker on AWS
EC2,
Hi Dmitry!
Tapestry since 5.3 minify css and js on a fly. That's why your cpu hits
100%, at startup when tapestry warm up resources on first request and when
your site has low traffic.
A workaround to solve this problem is disable this feature.
Take a look at your AppModule in
@Contribute(Resou
Hi,
I'd also try to collect thread dump when you see this happening to get an
idea where the CPU is wasted.
On Thu, May 16, 2019 at 10:38 AM Mats Andersson
wrote:
> Do you have some scheduled services that could eat memory? I would
> suspect that the garbage collector is using most of that CPU.
Do you have some scheduled services that could eat memory? I would
suspect that the garbage collector is using most of that CPU. Monitor
the GC and how memory is used over time. Maybe there is a mismatch
between the memory configurations in Docker and the JVM.
It seems like it is repeatable, t
