task_factory man page
export an implementation of a Broker::TaskFactory.
SYNOPSIS
exact_task_factory [-o ior-file] [-n name]
glacial_task_factory [-o ior-file] [-n name]
max_decay_task_factory [-o ior-file] [-n name]
max_task_factory [-o ior-file] [-n name]
DESCRIPTION
Each of these utilities create and export a different
implementation of the Broker::TaskFactory CORBA interface.
This interface is used to produce objects that provide
per-task resource usage sensing and reservation adapta-
tion.
Available options:
-o ior-file
The output file for the object's IOR. (Default for
each factory: exact_task_factory.ior,
glacial_task_factory.ior, max_decay_task_fac-
tory.ior, max_task_factory.ior)
-n name
The name for the object in the NamingService.
(Default for each factory: ExactTaskFactory,
GlacialTaskFactory, MaxDecayTaskFactory, MaxTask-
Factory)
Available factories:
exact_task_factory
This factory produces ExactTaskAdvocate objects.
An ExactTaskAdvocate adapts the reservation to the
exact amount of resources consumed by the previous
period.
glacial_task_factory
This factory produces GlacialTaskAdvocate objects.
A GlacialTaskAdvocate adapts the reservation by
slowly changing the current values to the amount of
resources consumed by the previous period.
max_decay_task_factory
This factory produces MaxDecayTaskAdvocate objects.
A MaxDecayTaskAdvocate adapts the reservation by
changing it to the maximum observed usage over some
number of periods. Thus, the advocate can adapt to
somewhat unpredicatable usage patterns without get-
ting stuck in a local maxima.
max_task_factory
This factory produces MaxTaskAdvocate objects. A
MaxTaskAdvocate adapts the reservation by changing
it to the maximum observed usage.
SEE ALSO
manager_server(1)
AUTHOR
The Alchemy project at the University of Utah.
NOTES
The Alchemy project can be found on the web at
http://www.cs.utah.edu/flux/alchemy
CPU Broker 0.5 2003/09/02 16:32:16 TASK_FACTORY(1)
Man(1) output converted with
man2html