Chapter 6: Performance Optimization
If you want to delete the cache, see
Deleting the Cache .
For debugging information, see
Debugging .
Limitations
l
The following Javadoc invocations are currently not supported: o Javadoc is invoked indirectly, such as through a wrapper script o The rule body recursively invokes eMake o
If Javadoc is named something other than "javadoc" l
Javadoc caching is sensitive to changes in
*.java
wildcard outcomes in directories that are actually read by the job, and any new subdirectories thereof.
l
Currently,
#pragma cache ...
cannot be applied to patterns as such, only to explicitly specified targets (though the commands may be provided by a pattern).
l
Windows is currently not supported.
l
The Javadoc caching feature does not detect the need to rebuild Javadoc files in these cases: o Changes to input files and programs that are used by a rule body but that Accelerator does not virtualize (because they are not located under
--emake-root=...
).
o Changes to non-filesystem, non-registry aspects of the environment, for example, the current time of day l
If a rule job checks the existence or timestamp of a file without reading it, Javadoc caching may not invalidate its cached result when the file is created, destroyed, or modified. However, Javadoc caching will detect when files matching "*.java" (or the pattern specified by "-readdir") are added or removed from directories read by the rule body, or any new subdirectories thereof. In that case eMake will rerun
Javadoc.
Schedule Optimization
How it Works
Schedule optimization uses performance and dependency information from previous builds in order to optimize the runtime ordering of jobs in subsequent builds.
This approach can improve performance on the same number of agents (compared to v7.0, or compared to v7.1
when the requisite information is not available), and enables eMake to realize the 'best possible' build performance for a given build with fewer agents.
Using Schedule Optimization
Schedule optimization is enabled by default, but it has no effect if scheduling data files are not available.
Emake automatically generates the scheduling data file in the asset directory (
.emake
by default) in the sched subdirectory under a platform-specific directory such as
Linux
,
SunOS
, or win32
. For example, on Linux the scheduling data file is found in
.emake/sched/Linux/emake.sched
.
The next eMake build that uses the scheduling data file will have improved performance.
Disabling Schedule Optimization
To disable schedule optimization, add the following to the command-line:
6-9
