We have a site with a very database, it's still running a cloning operation over 2 hours later, and for 1.5 hours of that time site performance went from 1.5 second page loads to 30 seconds, with occasional 502s. This is completely impractical and now we're questioning the viability of Cloudways for our large enterprise sites (and this site is running on a dedicated AWS CO 9XL instance). We have not seen live site performance this bad during cloning on other managed WP hosts (we moved it from a Pressidium Enterprise install, over there we had no issues cloning to Staging).
Ryan
We have a site with a very database, it's still running a cloning operation over 2 hours later, and for 1.5 hours of that time site performance went from 1.5 second page loads to 30 seconds, with occasional 502s. This is completely impractical and now we're questioning the viability of Cloudways for our large enterprise sites (and this site is running on a dedicated AWS CO 9XL instance). We have not seen live site performance this bad during cloning on other managed WP hosts (we moved it from a Pressidium Enterprise install, over there we had no issues cloning to Staging).