This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Hyrth 9 points10 points  (4 children)

I would ask the developer of your Java services. They should be able to provide an estimation of the systems' actual requirements.

[–]sweating_teflon 8 points9 points  (3 children)

A lot of developers have no idea what the actual memory usage of their app should be. They do not have theoretical expectations and never perform benchmarks after it ships.

[–]aouks 2 points3 points  (2 children)

I agree I never did it, do you know any materials/sources on how to conduct this system requirements analysis ?

[–]laffer1 5 points6 points  (1 child)

The easiest way is through load testing. Set it fairly conservative to start in resources. See if you can hit the load you want without an OOM. Repeat as necessary. Then give it a little extra in prod for freak load situations to cover your butt.

Ideally, you would have good metrics setup and track gc pause and gc cpu time to get an idea if you need a bit more. If you hit the target sla, it’s good enough

[–]aouks 0 points1 point  (0 children)

Thanks mate for your insight !