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

Revise 2.0 memory footprint estimates in documentation #824

Open
yezr opened this issue Apr 12, 2024 · 0 comments
Open

Revise 2.0 memory footprint estimates in documentation #824

yezr opened this issue Apr 12, 2024 · 0 comments

Comments

@yezr
Copy link
Collaborator

yezr commented Apr 12, 2024

Actionable followup to #559. In it, Armin says

tabulating 300,000 CVRs out of 1,500,000 records takes 500mb additional memory (in addition to 350mb used just to launch RCTab). That means we'd be able to support 2.4 million CVRs on a 4GB machine - plus/minus a bit, since the rest of the machine will use some memory, but the JVM would also garbage collect more often.

Let's test and confirm this.

Then update Section 03 - System Hardware Specification in the TDP. This currently has some ballpark estimates about how much memory is required for certain ballot thresholds and how long it will take. Let's review and confirm those.

Once we have new estimates, review priority of #559

@yezr yezr changed the title Revise 2.0 memory footprints in documentation Revise 2.0 memory footprint estimates in documentation Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

1 participant