You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 22, 2020. It is now read-only.
We’re hitting a bottle neck and mosql is not keeping up with the oplog. We’re generating about <1000 write ops per minute and all the systems are running on top of AWS (mongoDB, mosql, postgresql on RDS). It’s not clear what the bottleneck is since the CPU and RAM doesn’t seem to be a problem (on any of the instances) and we are using 2000 provisioned IOPS on the RDS and Mongodb sides. Any clues? Is there something in the mosql processing that we could optimize?
Thanks!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A question rather than an issue.
We’re hitting a bottle neck and mosql is not keeping up with the oplog. We’re generating about <1000 write ops per minute and all the systems are running on top of AWS (mongoDB, mosql, postgresql on RDS). It’s not clear what the bottleneck is since the CPU and RAM doesn’t seem to be a problem (on any of the instances) and we are using 2000 provisioned IOPS on the RDS and Mongodb sides. Any clues? Is there something in the mosql processing that we could optimize?
Thanks!
The text was updated successfully, but these errors were encountered: