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

Some datanommer queries are just too long #98

Open
abompard opened this issue Apr 23, 2024 · 0 comments
Open

Some datanommer queries are just too long #98

abompard opened this issue Apr 23, 2024 · 0 comments

Comments

@abompard
Copy link
Member

Some datanommer queries are too long to be practical, for example querying the number of messages with topic org.fedoraproject.prod.buildsys.build.state.change for user foobar in the entire datanommer DB takes about 2 minutes. It's unrealistic to run this on each incoming buildsys.state.change message. As a result, fedbadges is unable to cope with the amount of messages coming in.

I think fedbadges (or maybe datanommer.models) should develop a form of cached values. Fedbadges could cache the number of messages with a given topic and a given username, and this would go a looong way to make it faster. It would increase this number when a message comes in, and optionally rebuild the cache periodically. This cache could be stored in a Redis or memcached instance (in the same Openshift project or shared).

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