You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On page load, we score every single relic's potential against all characters. This n x m operation is growing pretty fast with 2000 relics and 60+ characters now, and this can take multiple seconds on page load
Goal
Look into if this is necessary and how we can optimize
The text was updated successfully, but these errors were encountered:
I think we should analyze the scoring algorithm and look for repeated work - there's going to be a lot of calculations that can be cached between characters. For example all the 0.75/1/1/1 crit characters can probably reuse the same scoring results between each other
Motivation
On page load, we score every single relic's potential against all characters. This n x m operation is growing pretty fast with 2000 relics and 60+ characters now, and this can take multiple seconds on page load
Goal
Look into if this is necessary and how we can optimize
The text was updated successfully, but these errors were encountered: