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

Investigate using the message index in the ChainStore #10663

Closed
fridrik01 opened this issue Apr 13, 2023 · 2 comments
Closed

Investigate using the message index in the ChainStore #10663

fridrik01 opened this issue Apr 13, 2023 · 2 comments
Assignees

Comments

@fridrik01
Copy link
Contributor

fridrik01 commented Apr 13, 2023

See Epic: Message Index #10536 for background

In PR #10452 we introduced a Message Index to Lotus which is backed by a sqlite backend and allows us to speed up certain calls like StateSearchMessage.

We may be able to use this index in the ChainStore, but it's unclear. We should investigate (see #10452 (comment) for context).

@fridrik01 fridrik01 self-assigned this Apr 13, 2023
@fridrik01 fridrik01 mentioned this issue Apr 13, 2023
8 tasks
@Stebalien Stebalien changed the title Make the index owned and used by the chain store Investigate using the message index in the ChainStore Apr 18, 2023
@maciejwitowski
Copy link
Contributor

Lowering the priority based on info from @fridrik01

It turns out that that task was more an "investigation" rather than actually refactor since it was not clear how much that change will improve performance

@Stebalien
Copy link
Member

Benchmarking determined that this isn't required.

@Stebalien Stebalien closed this as not planned Won't fix, can't repro, duplicate, stale Oct 4, 2023
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

No branches or pull requests

3 participants