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

nitro-cli: Update enclave boot timeout based on allocated memory #633

Merged
merged 1 commit into from
Jul 17, 2024

Conversation

mariusknaust
Copy link
Contributor

@mariusknaust mariusknaust commented Jul 10, 2024

Before pull request #310 the enlave boot timeout was calculated based on the allocated memory size. We reintroduce this heuristic in addition to the heuristic based on the eif size, since we observed timeout violations for large allocated memory sizes.

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@mariusknaust mariusknaust force-pushed the main branch 2 times, most recently from c63fdba to 52bc29f Compare July 10, 2024 14:01
@mariusknaust mariusknaust changed the title nitro_cli: Update enclave boot timeout based on allocated memory nitro-cli: Update enclave boot timeout based on allocated memory Jul 10, 2024
eugkoira
eugkoira previously approved these changes Jul 10, 2024
foersleo
foersleo previously approved these changes Jul 10, 2024
@mariusknaust mariusknaust marked this pull request as draft July 12, 2024 10:24
Before pull request aws#310 the enlave boot timeout was calculated based on
the allocated memory size. We reintroduce this heuristic in addition to
the heuristic based on the eif size, since we observed timeout
violations for large allocated memory sizes.

Signed-off-by: Marius Knaust <[email protected]>
@mariusknaust mariusknaust merged commit 9124741 into aws:main Jul 17, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants