Skip to content
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

libsql: Improve WAL frame push logic #1817

Merged
merged 1 commit into from
Nov 14, 2024
Merged

libsql: Improve WAL frame push logic #1817

merged 1 commit into from
Nov 14, 2024

Conversation

penberg
Copy link
Collaborator

@penberg penberg commented Nov 14, 2024

The server returns its maximum frame number so let's use that as a hint to avoid pushing frames it already knows about. IOW, let's start by sending the first frame in the WAL, but immediately skip to a the server's max frame number. Later we should also cache the server max frame number on client side to make the first push start from the right frame.

The server returns its maximum frame number so let's use that as a hint
to avoid pushing frames it already knows about. IOW, let's start by
sending the first frame in the WAL, but immediately skip to a the
server's max frame number. Later we should also cache the server max
frame number on client side to make the first push start from the right
frame.
@LucioFranco LucioFranco added this pull request to the merge queue Nov 14, 2024
Merged via the queue into main with commit 89b3460 Nov 14, 2024
18 checks passed
@LucioFranco LucioFranco deleted the optimize-wal-push branch November 14, 2024 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants