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.

Sign up for GitHub

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

Jump to bottom

Cost model impact for new prior lake database table #197

Open
frankinspace opened this issue Jun 27, 2024 · 2 comments
Open

Cost model impact for new prior lake database table #197

frankinspace opened this issue Jun 27, 2024 · 2 comments
Assignees
@torimcd
Labels
documentation Improvements or additions to documentation
Milestone
Add prior Lake da...

Comments

@frankinspace
Copy link
Member

  • Determine storage estimates for new data and inform @jimmie
@frankinspace frankinspace added the documentation Improvements or additions to documentation label Jun 27, 2024
@frankinspace frankinspace changed the title Cost model impact for new database table Cost model impact for new prior lake database table Jun 27, 2024
@torimcd torimcd self-assigned this Jul 29, 2024
@torimcd
Copy link
Collaborator

torimcd commented Jul 29, 2024

compare to the reach & node table size

@torimcd
Copy link
Collaborator

torimcd commented Aug 16, 2024

Expected capacity for each of the individual lake products (prior, observed, unassigned) is approx 1.7 million records/day (mean estimate), which corresponds to ~90 GB/month, ~1 TB/year per subcollection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@torimcd torimcd

Labels
documentation Improvements or additions to documentation
Projects
SOTO PI 24.3
Status: ✅ Done
Milestone
Add prior Lake data to Hydrocron
Development

No branches or pull requests
2 participants
@torimcd @frankinspace