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

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

I set up a master and a read-only MySQL database using DigitalOcean’s DBaaS service and subjected it to heavy write loads. I noticed that the “Seconds Behind Master” metric increased significantly. Specifically, during a 300-second period of data insertion on a replica node with 2 cores and 4 GB of RAM, CPU utilization reached 100%. The lag times were approximately 1500 seconds with an insertion rate of 7,000 records per minute, and 250 seconds with a rate of 2,000 records per minute.
I observed that the ‘log-slave-updates’ parameter was enabled. From my past experience, this setting tends to significantly impact replication lag. Although the retrieved GTID remained in sync with the master, the executed GTID lagged behind. I’m curious about the rationale behind DigitalOcean’s default choice to enable this parameter. Could there be a specific reason why it is not set to ‘OFF’?
Chris
twcinnovations
richard.wilson
richard.wilson
richard.wilson
rich
64c835749e2e4bf7a2259c9e896737
Yakin
caio_fr_sp
Abhishek M S
lnxfsf