After deployment, everything works slowly for 10 minutes, then normalizes. Why?

This behavior is often associated with a "warm-up" of the application after deployment. In the first minutes after JVM startup, it performs bytecode compilation into native code (JIT compilation), which requires resources and slows down performance. Additionally, loading and initializing caches, connection pools, classes, and other resources may occur.

Examples of causes:

• JIT compilation of frequently called methods.
• Initialization of caches (e.g., Hibernate second-level cache).
• Loading and compiling JSPs or templates.
• Connecting to external services and establishing connections.

To reduce the effect:

• Use application warm-up by running test requests immediately after deployment.
• Configure JVM for more aggressive compilation.
• Optimize resource initialization.

This is normal behavior for Java applications with JIT compilation.