After major upgrade, Spectrum memory utilisation has increased from around 60% to over 90%
Article ID: 447991
Updated On:
Products
Issue/Introduction
Since upgrading to NetOps 25.4.9 from 24.3.7, memory on the java process on Spectrum server (combined OneClick / SpectroSERVER) is running at 91% where at had been hovering around 40 to 60%.
What are the reasons for this?
Environment
DX NetOps Spectrum upgrade from 24.3.x to 25.4.x or later
Cause
An upgrade straight from 24.3.7 to 25.4.9, is a substantial jump. While there's absolutely no problem in that kind of jump, 25.4.9 does have a bigger code base due to new features/functions.
Resolution
As this is a combined OC/SS server managing ~33,600 models with multiple integrations actively running the normal memory recommendation is double. As well, if are many integrations such as:
- Okta SAML SSO (localhost.log),
- SRM/Crystal Reports threshold archivers,
- SDN Manager integration,
- NIM (ca-nim-sm),
- etc
Then the memory requirement is further increased.
New releases, such as 25.4.9, carry a genuinely larger baseline memory/code footprint than 24.3.7 (with new log4j-appserver stack, added --add-opens JVM module flags, several releases' worth of accumulated feature code), and it appears this machine is possibly under-provisioned considering. The 40–60% headroom under 24.3.7 was likely masking marginal sizing; 25.4.9's larger footprint ate into that slack.
We advise a minimum of 32GB of RAM for this type of setup (combined OC/SS with integrations) but higher is always better.
Additional Information
Always check the Spectrum Sizer before deploying a major new release so as to ensure adequate resources are provisioned for the servers:
Feedback
