Even if it sounds good there are 2 current issues with such an approach:
- In the current backend implementation all cards that are using optimized preset are marked as modified. Consider the following scenario:
a. User makes some reviews on device A. Does not sync.
b. User opens device B and auto-optimization is triggered.
Result: not synced reviews from device A are lost, because “modification” on device B is newer. - In this comment L.M.Sherlock stated: “According to my recent analysis, the new parameters are better than the old one in only 60% cases if you re-optimize every 1000 reviews.”