Next: Developer-defined Performance Metrics
Up: Standard Estimation Tags
Previous: Standard Estimation Tags
Contents
To access to the existing default performance estimation
routines (as described in Chapter 8), the following
functions are available to facilitate the construction of custom
performance estimation functions:
- FAST- and NWS-based performance estimation metrics can be used in the plugin scheduler.
See the Section 8.2.2 for information on how to use them.
- The time elapsed since the last execution (to enable
the round-robin scheduler) is stored in an estimation metric vector
by calling
int diet_estimate_lastexec(estVector_t ev,
const diet_profile_t* const profilePtr);
with an appropriate value for ev and the
profilePtr corresponding to the current DIET request.
- The number of waiting jobs when using the maximum concurrent jobs
limit is stored in an estimation metric vector by calling
int diet_estimate_waiting_jobs(estVector_t ev);
- CoRI allows to access in an easy way to basic performance
prediction. See Chapter 8.3 to know more about the use of it.
In the future, we plan to expand the suite of default estimation
metrics to include dynamic internal DIET system state information
(e.g., queue lengths).
Next: Developer-defined Performance Metrics
Up: Standard Estimation Tags
Previous: Standard Estimation Tags
Contents
DIET Team - 2008-07-17