The biggest "?" is about operation time. This cleanup also takes lot of time and is cpu and IO intensive. The right moment to do it is after heavy database writting, that is refresh. Cron job also was suggested as an idea. But consideer the cron job too random about "when" to do it, and also problematic f it start working when you are using YaST or the applet is checking for updates (it is safe, but you will get a lock message). Our current idea is to do it on refresh but using a time threshold. And making it configurable of course.
More ideas are welcome.
Is it safe to assume the cleanup intensity is dependent upon the level of fragmentation and time between cleanups? Just a thought, but would it maybe make sense to add the cleanup process as a SuSEconfig function, to run after package installation? Not that we should really strive to make SuSEconfig take even longer than it does already, but users are already conditioned to waiting for that process to run after Yast completes, they'd have a visual indication as to what is occurring, and if it runs regularly then would the cleanup procedure be quicker and less intense? Power users could of course disable it or run it at the time of their choosing, but maybe as a default setting it may not be too much of a load. Cheers, KV --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org