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

persist LC data across restarts #3823

Merged
merged 7 commits into from
Jun 30, 2022
Merged

persist LC data across restarts #3823

merged 7 commits into from
Jun 30, 2022

Conversation

etan-status
Copy link
Contributor

With the Altair spec LightClientUpdate structure taking its final form
it is finally possible to persist LC data across restarts without having
to worry about data migration due to spec changes. A separate lcdataV1
database is created in the caches subdirectory to hold known LC data.
A full database with default settings (129 periods) uses <15 MB disk.

With the Altair spec `LightClientUpdate` structure taking its final form
it is finally possible to persist LC data across restarts without having
to worry about data migration due to spec changes. A separate `lcdataV1`
database is created in the `caches` subdirectory to hold known LC data.
A full database with default settings (129 periods) uses <15 MB disk.
@etan-status
Copy link
Contributor Author

lcdataV1.sqlite3.zip
Prater DB for testing.

@github-actions
Copy link

Unit Test Results

     12 files  ±0     857 suites  ±0   1h 10m 13s ⏱️ + 9m 9s
1 711 tests ±0  1 659 ✔️ ±0    52 💤 ±0  0 ±0 
9 940 runs  ±0  9 812 ✔️ ±0  128 💤 ±0  0 ±0 

Results for commit 4515851. ± Comparison against base commit c75d39f.

@zah zah enabled auto-merge (squash) June 30, 2022 10:41
@zah zah merged commit 499abd9 into unstable Jun 30, 2022
@zah zah deleted the dev/etan/lc-db branch June 30, 2022 13:04
@arnetheduck
Copy link
Member

why keep this in a separate database? this is supposed to be part of the "standard feature set" of every beacon node running the full protocol, so it should really live in the main db, no?

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.

4 participants