Bobcares

wesupport

CLIENT AREACall Us 1-800-383-5193
Bobcares

wesupport

Call Us 1-800-383-5193
Bobcares

wesupport

Call Us 1-800-383-5193

Need help?

Our experts have had an average response time of 13.52 minutes in October 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Amazon EC2 instance slow and unresponsive – How to resolve

by | Aug 14, 2021

Stuck with the ‘Amazon EC2 instance slow and unresponsive’ issue? We can help you with this!

Here, at Bobcares, we often receive similar AWS queries from our customers as a part of our AWS Support Services.

Today, let’s see the steps followed by our Support Engineers to resolve the EC2 instance’s slow and unresponsive issue.

 

EC2 instance slow and unresponsive

 
EC2 server becomes unresponsive or slow due to several reasons. It includes issues with the external service that the instance depends on, network connectivity issues, or disk thrashing.

Now we are going to see one of the common causes for the slowness or unresponsiveness and it is depleted I/O burst credits on the gp2 root volume where gp2 is the default storage drive for the root volume.
 

How to check I/O burst credit balance

 

  1. Log in to the AWS Management Console and open the Amazon EC2 console.

2. Select instances and then select the instance.

3. Select the Volume ID of the root device from the Storage tab.

4. Then select the Monitoring tab for the EBS volume, and from there we can find the Burst Balance metric.

If the burst balance is 0%, it means that all the credits are used. Also, the volume cannot burst above its baseline performance level. Therefore, we need to perform any of the following methods to resolve this issue with burst balance.
 

Evaluate the IOPS requirements and alter the volume

 

  1.  At first, open Amazon CloudWatch and we have to find the root EBS volume’s VolumeReadOps and VolumeWriteOps metrics.

2. Then find the peak levels of VolumeReadOps and VolumeWriteOps by using the CloudWatch Sum statistic.

3. Then add the two values.

For Example: VolumeReadOps = 865,000 and VolumeWriteOps = 186,000

Total sum = VolumeReadOps+VolumeWriteOps = 1051000

4. Then divide the total sum by the no. of seconds in the measurement interval to estimate how many IOPS are needed.

If the Measurement interval is 10 minutes, that is 600sec, then IOPS = 1051000 / 600 = 1752

The baseline performance for gp2 volumes scales at 3 IOPS per GB of volume size. Therefore a volume with 1752 IOPS must be scaled up to 584 GB(1752 / 3=584)to enhance the performance.

 

Modify the distribution of workload

 
If we have multiple applications in our Amazon EC2 instance, then it will compete for the root EBS volume’s IOPS. The IOPS demand will increase as the workload increases. For enhancing the performance of instances, we need to consider using additional non-root EBS volumes and root volume for your applications and for the operating system respectively.

[Need help with more AWS queries? We’d be happy to assist]
 

Conclusion

 
To conclude, today we discussed the steps followed by our Support Engineers to help our customers to resolve the ‘Amazon EC2 instance slow and unresponsive’ issue.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF