- Newest
- Most votes
- Most comments
Hello Jon!
For troubleshooting the issue of not reaching the expected 80% memory usage during AWSFIS memory stress tests on EC2 instances, make sure your monitoring tools like CloudWatch Agent are correctly capturing memory metrics. It's also important to check that the baseline memory consumption by the OS and background processes isn't too high before the stress test begins. Adjusting the parameters of stress-ng or trying it directly on an instance might reveal more about its impact on memory usage. Consider the possibility that t2.micro instances may not have sufficient resources for the intensity of your test, so experimenting with instances that have more memory could offer better results. Ensuring that all necessary dependencies for stress-ng and the AWSFIS-Run-Memory-Stress document are installed is crucial. Finally, review your CloudWatch alarms to make sure they're set up to accurately detect the conditions you're testing for.
I'm here to help.
Relevant content
- Accepted Answerasked 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago