Skip to content

Conversation

@tsunyoku
Copy link
Member

@tsunyoku tsunyoku commented Nov 28, 2025

image

Addresses part of #12556.

There's probably a non-zero chance that the time required to recalculate top plays for each country is too much on a production-sized index, but I don't have a good way to measure this nor make assumptions. In the worst case, country-specific top plays could fetch a lower score count, or maybe the country recalculation could be split into a separate command that runs less frequently?

@nanaya
Copy link
Collaborator

nanaya commented Nov 28, 2025

yeah this takes 30 minutes compared to 30 seconds for global only...

I doubt reducing count would help - it's most likely the sorting and filtering that is taking the most time.

@tsunyoku
Copy link
Member Author

How about a separate command that updates less frequently then?

@nanaya
Copy link
Collaborator

nanaya commented Nov 28, 2025

there's probably a way to get the whole thing in one go

also the plan is to increase the frequency, not reducing it...

@tsunyoku
Copy link
Member Author

The idea behind updating less frequently was to prevent updates of the global top plays just because the country one is slower. I agree reducing frequency is not ideal.

I'm not immediately sure of any ways we can do the whole thing in one go, at least if you want the country top plays to be equally populated, but if you have a direction to point me in then I can try figure it out.

@nanaya
Copy link
Collaborator

nanaya commented Dec 13, 2025

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.

2 participants