PerfectScalePerfectScale

HANDS-ON OPTIMIZATION WORKSHOP 

Java on K8s: The Startup vs. Steady-State Sizing Dilemma

October 28, 2026 at 11 AM ET

Save Your Seat!

Step 1 of 2

PerfectScale needs the contact information you provide to us to contact you about our products and services. You may unsubscribe from these communications at any time. For information on how to unsubscribe, as well as our privacy practices and commitment to protecting your privacy, check out our Privacy Policy.

Give a JVM enough CPU to boot fast and you pay for that boot forever, long after the pod settles and needs a fraction of it.

Kubernetes can now resize a running pod without restarting it, stable in 1.35 and on by default in 1.36.

This session covers how to size a pod for its boot, then shrink it once it's actually running.

What you'll walk away with:

  • What the JVM boot spike is, and why it hits both CPU and memory
  • What it costs you in over-provisioned requests, throttling, OOM kills, and slow or failed rollouts
  • How AOT compilation, JVM flags, and runtime tuning flatten the spike before Kubernetes ever sees it
  • How to size pods for steady state and still boot safely, with an in-place resize down from the spike, automatically, no restart

Who is this session for:

Platform engineers, SREs, and Java developers running JVM workloads on Kubernetes, especially anyone who has already provisioned pods to survive a startup spike and never revisited them.

Meet your speakers

Vikram Seshadri

Vikram Seshadri

Sr. Evangelist, DoiT

Vikram Seshadri spent eight years in platform engineering in the fintech space, including a stint as Senior Vice President leading EKS platform engineering at Citi. Now a Senior Evangelist for Enterprise Platforms at DoiT, he helps engineering teams solve the hard operational problems of running Kubernetes at scale: reliability, cost, and everything in between.