misersubmit(4)                                                misersubmit(4)



NAME
     misersubmit - resource schedule list

DESCRIPTION
     The miser_submit command allows the user to specify the resource schedule
     of a particular job in a file. The resource is a list of resource
     specifications, called segments, that define the resource requirements of
     a particular job. A resource specification is a tuple of CPUs, memory and
     wall clock time. Currently Miser only supports resource schedules
     consisting of one segment. A segment also has additional optional fields
     defining how the job is scheduled.

     The resource file consists of a list of segments. Each segment must begin
     with the token SEGMENT and have the number of CPUs, memory, and wall
     clock time specified. In addition to the resources, it is also possible
     to specify additional scheduling parameters.

EXAMPLE
     An example resource schedule list for an application that requires 10
     CPUs, 100 megabytes of memory, and 100 minutes of wall clock time:

     #resource schedule
     SEGMENT
     TIME 100m
     NCPUS 10
     MEMORY 100m


SUMMARY
     Commands are newline terminated, characters following the comment
     delimiter are '#' are ignored, case matters, each new segment must begin
     with the token SEGMENT and must have the number of CPUs, memory and wall
     clock time specified.

     The valid tokens are:

     SEGMENT
          Defines the begining of a new segment of the resource schedule.

     NCPUS cpus
          The number of CPUs that the segment can use.

     MEMORY memory [g|m|k]
          The maximum amount of memory that can be used at any one point. The
          memory is specified by a positive integer followed by a unit of g
          for gigabyte, m for megabyte, and k for kilobyte. If no unit is
          specified the value is assumed to be bytes.

     TIME time
          The time is the product of the total wall clock time per CPU and the
          number of CPUs. The time can either be specified by a positive
          integer followed by an h for hours, m for minutes, or s for seconds.



                                                                        Page 1

misersubmit(4)                                                misersubmit(4)



          The time may also be specified by a string of the form hh:mm.ss.

     STATIC
          This is an optional field. A segment that is STATIC has the property
          that an application will only run when the segment is scheduled to
          run. It will not run earlier even if there are idle resources
          available to the application.

     MULTIPLE number
          If a miser policy cannot schedule an application with the number of
          CPUs requested, the miser policy may try to schedule the application
          with fewer CPUs. This option allows the user to specify what
          multiple of CPUs may be considered.  For example, if an application
          can only be run using CPUs in multiples of two, the multiple value
          specified would be two. If no value is specified the default is one.

     EXCEPTION type
          This is an optional field. The type parameter may only be "KILL".
          Future versions of miser will support additional fields.

SEE ALSO
     miser_submit(1).

































                                                                        Page 2