Question

Why is my new scaled droplet (8GB RAM - 4 vCPUs) is 4 times slower than the old one?

Last Friday, August 11th 2018, I scaled my VPS for my website. As I started to receive more and more requests for LRC Maker and Downloads (Lyrics files), my CPU crossed 100% multiple times, and was averaging 80%.

The Apache server in the old VPS 4GB RAM and 2vCPUs used to load the Main Page in 200-250ms, now the new one with 8GB RAM and 4cCPUs is loading it in 900-1200ms. Just some minutes before the scale, the speed was still excellent. Now all the pages are taking 4x more times than before, I even started to loose some pageviews that kept until then increasing fastly.

I just try to update /etc/resolv.conf, without rebooting, but with no success. What could be behind such a slow performance?

Ubuntu 14.04, Apache 2.4, PHP 5.6, MySQL 5.5.9, Laravel 5.0, Same Codes as before…


Submit an answer


This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

jarland
DigitalOcean Employee
DigitalOcean Employee badge
August 13, 2018
Accepted Answer

Hello friend!

Sorry to hear about the trouble this is giving you. The source of the slowdown could be anywhere, and finding it is not always an easy task. It could be anything from a package upgrade going live after the reboot that came along with the resize, to a problem with our hypervisor. To rule out external factors, I’ve given you some credit to cover the cost of creating a snapshot and spinning up a new droplet. This will help you to determine whether the problem is most likely inside of your operating system or outside of your droplet.

If it is determined to be external, open a ticket with our support team and let us get that documented on your account as we work through it (I saw no clear evidence that it is, but that is not always conclusive). If it is determined to be internal, you’re going to need to troubleshoot every layer of your software stack until you find where it is slowing down. That may require watching MySQL queries, running strace on a PHP process, and perhaps even simple use of things like gtmetrix.com.

Kind Regards, Jarland

Yesterday August 21th, I have done the Proxy Server with my Staging Server, it’s working great. And the new one is a bit faster. Today I started to do it for production, power down the droplet at 2h46 PM, take the SNAPSHOT. Now it’s 5h54 PM (3 hours +), and that SNAPSHOT is still creating. 80GB Hard Drive and about 50GB of Data inside.

I’m planning in the future to move the static audio files to an Object Storage. I’d like to know if there is a problem with my SNAPSHOT so that I can cancel it and serve the website as it is for the moment.

This comment has been deleted

    Try DigitalOcean for free

    Click below to sign up and get $200 of credit to try our products over 60 days!

    Sign up

    Become a contributor for community

    Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

    DigitalOcean Documentation

    Full documentation for every DigitalOcean product.

    Resources for startups and SMBs

    The Wave has everything you need to know about building a business, from raising funding to marketing your product.

    Get our newsletter

    Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.

    New accounts only. By submitting your email you agree to our Privacy Policy

    The developer cloud

    Scale up as you grow — whether you're running one virtual machine or ten thousand.

    Get started for free

    Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

    *This promotional offer applies to new accounts only.