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

chore: remove writes to snapshot #118

Closed
wants to merge 5 commits into from
Closed

Conversation

arriqaaq
Copy link
Contributor

@arriqaaq arriqaaq commented Nov 5, 2024

No description provided.

@arriqaaq arriqaaq force-pushed the perf/remove-snapshot-writes branch 2 times, most recently from b8193bb to b196cc3 Compare November 5, 2024 11:24
@arriqaaq arriqaaq force-pushed the perf/remove-snapshot-writes branch 3 times, most recently from 069b260 to d3ca252 Compare November 5, 2024 12:39
@arriqaaq arriqaaq force-pushed the perf/remove-snapshot-writes branch from d3ca252 to dba4d3f Compare November 5, 2024 13:06
Base automatically changed from chore/improve-benchmarks to main November 6, 2024 07:20
.collect();

// Sort by key
entries.sort_by(|a, b| a.0.cmp(b.0));
Copy link
Contributor

@gsserge gsserge Nov 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it might actually be better to change the Write Set from HashMap to BTreeMap. That way you won't have to collect the latest values upfront in a vector and sort them, since BTreeMap's iterator is ordered. Maybe this will be enough to keep the scan perf in par with the current one.

@gsserge
Copy link
Contributor

gsserge commented Dec 18, 2024

Handled in #151

@gsserge gsserge closed this Dec 18, 2024
@gsserge gsserge deleted the perf/remove-snapshot-writes branch December 18, 2024 08:48
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