always use host database and make protected;

read relative cpu from build log;

prefer extensible next_node_info in build process over process_options in build engine (which needs the final node info anyway);

added start date to build jobs, e.g., for build time estimation;

added initial version of benchmark module, e.g., to compare performance of different hosts; added benchmark operation to build cluster;

generalized node infos: allow addressing of numa node segments via relative cpus; add more node options and process policy options using taskset as alternative to NUMA for more fine-grained cpu controls (e.g., for cpus with heterogeneous cores in the same NUMA segment);

add information about static host resources such as available NUMA nodes, cpus, etc. (e.g., for offline build planning);