Confirmed users
595
edits
(→Design) |
|||
Line 40: | Line 40: | ||
=== Vacuum on idle === | === Vacuum on idle === | ||
Every month (or 2 months), after a relatively small idle time (to avoid hitting standby or hibernation) like 5 minutes we could start analyzing dbs using our fragmentation guess. If there are dbs that needs vacuuming show to the user a window saying something like "App is going to perform maintenance of its databases" with a 10 seconds countdown and a cancel button. When countdown expires a progressbar starts. the user can still cancel the process (we cannot interrupt a single vacuum, but we could stop vacuuming next dbs in the list) with the cancel button. | |||
Advantages: | Advantages: | ||
* won't hit a specific moment in which the user is doing something | * won't hit a specific moment in which the user is doing something |