-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Integrations of Load balance & Easy days #3116
Comments
Yep - my initial thought is we could store the counts per day there, and adjust the counts each time a card is answered. One thing to think about is the long tail - large/old collections could potentially have thousands or tens of thousands of different due dates. What if we limited the features to a shorter time span, such as cards due in the next 3 months? For things like load balancing, it's probably not so useful to be balancing cards when they're so far out anyway, and as they become closer, younger cards would still be load balanced on those days. WDYT? |
It's totally acceptable. And we can also skip load balancing if the next due date is pretty far. |
An important question: when will Load Balancing be applied? After each review is probably too computationally expensive, although I may be underestimating Rust. So I'm guessing when the user clicks "Sync"? |
If we have a cached dictionary of daily due numbers, balancing can happen as cards are answered. |
Question: Will there be a way for us to use load balance not only for the collection but also for a particular deck? Someone bought this up before when there was no plan to add this feature in Anki. (For me, cards in some decks take longer time so want to prioritise their balancing) |
These two features require Anki to maintain a record of how many cards are due on each day.
As an initial idea, we may maintain this record in
StateContext
.The text was updated successfully, but these errors were encountered: