-
Notifications
You must be signed in to change notification settings - Fork 384
Embedded replica syncs a lot during UPDATE/INSERT/COMMIT #2079
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It will be helpful to understand the server stack you are syncing against to make sure everything is up2date. It seems from your screenshot that you are syncing against the Turso Cloud. In that case it would be helpful to know the URL, and then we can check |
Also would be interesting to understand your workload. Do you have enough writes to rewrite the database 20x over? Do you still see issues with high sync bandwidth if you stop writing for a period of time ? |
@Resonious Are you on our discord server? (makes it easier to share private / sensitive information). if so, I'd like to debug this with your db and understand your workload. |
Yes, Turso Cloud. I'll share some info on Discord. Workload is mostly reads actually, which is why I'm a bit surprised / suspect something is wrong. |
Actually I'll just share the DB URL here for now: I am in the server under the name Resonious in case you want to send me a message! |
Uh oh!
There was an error while loading. Please reload this page.
I have one server that's a little far from the database. Thus, I'd like to use embedded replica mode to speed things up a bit. Problem is, it actually slows things down most of the time. (Rust client)
Reads are very fast as expected (love it), but writes and transactions result in tons of frames being pulled in:
Pretty much every mutation to the database looks like 👆, despite calling
sync
every 5 seconds, and no other traffic.Additionally, I'm racking up sync bandwidth like crazy
The amount of syncs I've done looks like I could've downloaded every DB in my account 20 times... Is this expected? Let me know if there's anything I can do to further troubleshoot.
The text was updated successfully, but these errors were encountered: