____________

Java Monitor for Task Management

____________

The Java monitor is designed to ease the job of the system administrator. It contains three pages of information: machine records, job records and daemon status.

In the machine record page, the following information for each participating machine is displayed:

  • the name of the machine
  • the status of the machine (which can be heavily loaded, moderately loaded, lightly loaded, idle, runnable, or running a remote job)
  • the keyboard idle time
  • the time when the machine record was last reported
  • the job (if any) that is currently running on the workstation
  • the number of jobs that were submitted to the workstation and are currently queued
  • the average waiting time until a job is first executed after its arrival
  • the percentage of local CPU time consumed by jobs submitted to the workstation
  • the priority list used for each workstation

    • In the job record page, the following information is displayed for each job that is currently queued or being executed:

  • the job id
  • the owner of the job
  • the status of the job (which can be unexecuted, running, checkpointing, suspended, or idle). Note that an idle job means that the job was executed for some amount of time, but is currently idle.
  • the server workstation (if any) which is currently executing the job
  • the time at which the job was submitted
  • the time at which the job was started
  • the time at which the job was finished
  • the percentage of local CPU time used by the job
  • the percentage of remote CPU time used by the job
  • the size of executable
  • the command used to submit the job

    • In the daemon status page, the status of the daemons at each participating workstation is displayed. A red dot means that the daemon is alive.

    The monitor runs on a machine (which needs not be one of the participating workstations), and communicates with a statistics collector daemon that runs at each participating machine. The statistics collector daemon is implemented in such a way that it behaves like a "remote shell" daemon. That is, it takes the command from a socket, executes it locally and then returns the result to the command initiator (i.e., the Java monitor). In this manner, the Java monitor has full control of the commands to invoke, the arguments that goes with the commands, and when to invoke the commands.

    Return to Project Home Page or Software Demo Page .
    Date last modified -- August 12, 1998
    Direct comments concerning this WWW site to: jhou@ece.osu.edu