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

Explore alternatives to constantly fetching entire election def for auth lib #4790

Open
arsalansufi opened this issue Apr 24, 2024 · 0 comments

Comments

@arsalansufi
Copy link
Contributor

arsalansufi commented Apr 24, 2024

When an election definition is large, say, because it has a large seal, this seems to bog the system down.

Copying from Slack:

I know we're constantly refetching the election def from the store to pass to the auth lib. we initially planned to cache the relevant data in the auth lib, but as we all know caching is hard / error prone. and ultimately decided that the election def was too small for this to matter. a big seal definitely breaks that assumption. for the auth lib use case, all we really need is the election hash. we could explicitly persist that in the DB and just refetch that

Link to Slack thread: https://votingworks.slack.com/archives/C06H2PBP0MU/p1712798609099009?thread_ts=1712790170.563049&cid=C06H2PBP0MU

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant