Why do xml.transform, derby and compiler take so long before they start?
They need to perform some preparatory work before measurements interval, which is done in a setup phase before the warmup and measurement period. Derby initializes and populates a database, The xml.transform benchmark makes one operation before measurement start to verify results fully, this includes canonicalization of output. The compiler benchmark gathers files information to reduce file I/O impact during measurements interval.
