Managed DB become very very slow

When I connect my Laravel Application using the localhost MySQL then it’s work very fast. But when I do connect my Application to the Managed DB, it’s become 5 times slower. I really wants to use the managed DB but not slower of course.


This is terrible. I cannot believe that Digital Ocean still hasn’t responded with a solution. Surely everyone must be considering to nolonger use Managed DB when the latency is this poor!

We have just experienced terrible latency on the Managed DB mysql setup.

50second to 1.3min latency when we have a basic load. we never had this problem when running mysql on a droplet directly.

Same issue here… it’s about 20 times less slower… it takes 75ms in average to fetch a single row by primary key from one table with 10 (small) columns.

Locally it’s 4 milliseconds. I cannot believe there is SOOO much latency ?!

Or is it the performance, settings tweaking not optimal on their side ?

I will switch tomorrow for another provider, will do some tests to find which managed DB provider has the best performance.

Same issue in 2022. I switched my laravel app from droplet based deployment to App Platform + Managed Database and got 5 times slower response. The old droplet is a Basic Shared CPU 2VCPU 4GB and the new instance is Pro Plan (App Platform) + Managed Database 2 GB RAM / 1 vCPU with current usage : RAM 18% CPU 1% (App Platform) and RAM 64% CPU 5% (Managed MySQL). Both of App Platform and Managed Database are in the same region

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

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.

Unfortunately this problem still persists and I cannot explain the problem to digital ocean. We couldn’t find a solution. I’m converting it to local. Don’t waste your time.

Make sure your db node and app server node are in the same VPC. Digital Ocean has two default VPC’s: one on one side of the continent, one on the other, and if your application sends packets between the two internally, you may be observing significant latency in production. Moving all of your application components to one side of the continent should fix the problem. -piousbox

Same problem here, Why is the digital ocean not taking this as a high priority and not providing the solution yet? Did we miss any setup for managed DB?

Quick response will get more sales…

ufff, thx you guys, I was thinking in move my app to managed database

I moved to Digital Ocean from AWS RDS primarily because, unlike Linode and Vultr they boasted managed database solution.

However, I have found the same as all of you; the performance is quite terrible.

If you want a direct comparison you can visit the following:

Droplet (8 GB RAM / 2 dedicated CPU / 25 GB Disk - MySQL version 8 - the same as managed) (1.5s)

Digital Ocean Managed Database: (8 GB RAM / 2 dedicated CPU / 25 GB Disk) (27.9s)

Mariadb 15 on local machine (4 GB Memory / 2 AMD vCPUs / 50 GB Disk) (0.744s)

As you can see (and test for yourself) the difference in performance is huge. I uploaded a video showing the difference - DO support said they never got it.

I also gave them the two last sites - they couldn’t see any difference, but explained away any performance drop with considerations of latency etc. etc. etc.

If you go to the shorter threads then there is little difference, but the ones I have posted above are longer threads and so require more queries.

I gave them links to these and then they said it was down to a difference in database engines: Mariadb is quicker than Mysql 8 and suggested I test on a droplet running this.

Then they closed the support ticket as resolved! Clearly they don’t want to accept there is an issue even though it couldn’t be clearer to see.

Yes, after installing Mysql 8 on another droplet you can see it is quicker as they say, but by 0.7s vs 1.5s (mainly down to latency of local to separate droplet) and still nothing like the 28s for their managed service.

I feel that all I get from Digital Ocean is fobbed off with excuses for essentially a poor product.

Are they being deliberately disingenuous about the fact that there are some real performance issues going on here with their managed database service that effectively render it useless?

I have to report similar issues. Had my react app running quite smoothly on a $5 droplet including the db. I am the only one who is actually accessing it so really low workload. Performance on my $5 droplet was about the same as on localhost.

React App built up in .5s with all data

Then I switched to a managed db inside the same Location and local network and everything changed. Now my load time is about 4-5s

Nothing else was changed. Localhost is still fast.

Sadly same issue here. We run high traffic news websites with 10’s of million pageviews a month and were facing issues with capacity. First we thought it were webservers but quickly figured out that mysql is not returning an answer in an acceptable time. Compared to a regular droplet running mysql we tested about 8x faster (with testing tool). Even te memory went from 80% to 10%.

I face exactly the same issue! This is a disaster…I only managed to find out it’s so much slower(100x slower) after migrated to the managed database. Initially, I thought it was the indexing that causes such issue. Export the database and import them to run on my local, it very quick! DO, this can’t be real. We have to solve this ASAP!

Hello @shahinKazi,

I liked your questions. There are so many people out there who has similar types of questions regarding database performance.

In your case I think it would be worth to look into improving latency of your database. There is no problem with Managed DB or un-managed DB. Only difference is in managed DB, engineers from DO will take care of your DB server. But it’s already optimized. Improving performance is stuff that you need to tweak by yourself.

But few things I need to mention here.

  • In localhost, there is near 0ms latency. That’s why it’s working well there I hope.
  • Try to launch your DB with high-availability settings (multi zone) or in the zone where your application is also hosted. It will improve much better.

Also I would like to request you to visit to understand performance metrics by DO for their managed DB.

Hope, it’ill help.