Hi,

I just checked in a change which dramatically reduces the startup time for the
install_wizard when it is invoked more than once. Instead of minutes it just
needs a few seconds now.

This corresponds to the following ToDo item on my list:

* avoid unnecessary wizard operations: similar to the md5sums for regenerating
  the package pool metadata caches we can avoid more operations and speed up
  the wizard considerably.

The implementation is by storing md5 checksums for certain files (actually
only for their metadata) in $OSCAR_HOME/tmp. For example the checksum of the
metadata of the prereqs is stored one by one at the first invocation of the
install_cluster wizard. At the next invocation the prereqs will not be
reinstalled again if their metadata didn't change. The same with the metadata
of the packages. If nothing chaged for the packages, there will be no attempt
to reinstall the core packages. Also there is a checksum over all config.xml
files. If they don't change, their XML content will _not_ be re-read and
re-added to the OSCAR database. All this saves a tremendous amount of
startup time.

If you want to force the execution of all parts of the wizard_prep script,
simply remove the relevant .md5 files in $OSCAR_HOME/tmp. This directory needs
to be removed at a "start_over", too. I didn't modify start_over, yet, maybe
somebody has time to do it.

By the way, I now renamed the pool.md5 checksum for the repositories and moved
it also to the $OSCAR_HOME/tmp directory.

Regards,
Erich



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to