Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

As a Product Owner I want that the memory allocated for Proxy component will be automatically adjusted at init phase of Security Server to correlate the amount of RAM memory to optimize the performance #1357

Open
9 tasks
raits opened this issue Sep 22, 2022 · 0 comments
Labels
hacktoberfest Issues included in Hacktoberfest help wanted Extra attention is needed

Comments

@raits
Copy link
Contributor

raits commented Sep 22, 2022

By default, the Proxy component is using heap memory at a minimum 100Mb and at a maximum 150Mb (-Xms100m -Xmx150m). This is too small for a virtual machine/server that has more memory than 1G RAM. By setting the Proxy's memory too small, it is limiting the performance of the Security Server in most cases.

The amount of RAM memory should be used as a base factor when deciding the amount of memory allocated for the Proxy component.

During the implementation of this ticket, the automatic detection of RAM memory and automatic Proxy memory allocation will be done.

Basic recommend settings for Proxy (and Signer) memory based on the amount of RAM are published at:
https://nordic-institute.atlassian.net/wiki/display/XRDKB/Recommended+Memory+Allocation+for+Proxy

The JIRA ticket this issue was created from can be found here: https://nordic-institute.atlassian.net/browse/XRDDEV-55

Acceptance criteria:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hacktoberfest Issues included in Hacktoberfest help wanted Extra attention is needed
Projects
Status: Todo
Development

No branches or pull requests

1 participant