3.1 Command Line Options

This topic identifies the individual command lineoptions recognized and/or required by Nitro.

In this topic:

• 3.1.1 Options
• 3.1.2 Command Line Options per Nitro Mode

3.1.1 Options

• Thread Count – The quantity of threads the Nitro workers should use when executing tasks. This option is mutually-exclusive with the Thread Ratio option.

  If this option and the Thread Ratio option are not given, a worker uses one task launch thread per OS core to which it is pinned.

  The primary reason for this option is to explicitly specify a task-launch thread count for Nitro running a specific single application, usually on homogeneous hosts.

  --thread-count <num>

• Thread Ratio – The ratio of task launch threads-to-OS "cores" the Nitro workers should use when creating task launch threads. This option is mutually exclusive with the Thread Count option.

  If this option and the Thread Count option are not given, the ratio is "1.0", meaning a worker uses one task launch thread per OS core to which it is pinned.

  Ratio is a positive real number (e.g., 1.5, 0.5, etc) that when multiplied with the count of OS cores to which a worker is pinned yields a count of the task launch threads it will use. The worker rounds the count to the nearest integer, with a minimum value of 1.

  The primary reason for this option is to allow a user to over-subscribe or under-subscribe the task-launch thread count appropriately relative to the OS core count of heterogeneous hosts (e.g., 1.5 means 6 threads for a quad-core host and 24 threads for a 16-core host).

  --thread-ratio <ratio>

• Assignment Size – The quantity of tasks the Nitro coordinator should pass to a Nitro worker at one time; default is 250.

  --assignment-size <num>

• Job Directory – Specifies the path for the directory where Nitro will place its Job Progress Log and Completed Task Log files.

  --job-dir <path>

• Job ID – Specifies the job ID for a specific Nitro run. The job ID may be used to create the job directory and certain file paths.

  --job-id <jobID>

• Coordinator Threads – Indicates to the coordinator how many threads to reserve for the coordinator when allocating cores to a local worker (when using "‑‑run-local‑worker" on the coordinator command line). Default is 2. Adaptive Computing recommends setting the <count> value to 1 if all jobs will use less than 20 nodes and setting the <count> value to 4 if the jobs require a large number of nodes (greater than 50) to run.
  

  This option overrides the --coord-threads setting in the nitro.cfg file.

  --coord-threads <count>

• Task Environment – Specifies the environment variables to set in the task's execution environment. This is used by the worker but is also needed on the coordinator's command line if running a local worker. Multiple values can be specified by separating name/value pairs with a comma.

  --task-env <ENVVARNAME=value[,...]>

3.1.2 Command Line Options per Nitro Mode

The table that follows identifies which command line options Nitro uses in worker or coordinator mode. Some command line options are used in both modes and are listed in this table in the "Both" row.

Nitro Mode	Command Line Option
Coordinator	‑‑assignment‑size ‑‑coord‑threads (if using ‑‑run‑local‑worker with the coordinator)
Worker	‑‑task‑env (if not using ‑‑run‑local‑worker with the coordinator) ‑‑thread‑count (if not using ‑‑run‑local‑worker with the coordinator) ‑‑thread‑ratio (if not using ‑‑run‑local‑worker with the coordinator)
Both	‑‑job‑dir ‑‑job‑id ‑‑task‑env (if using ‑‑run‑local‑worker with the coordinator) ‑‑thread‑count (if using ‑‑run‑local‑worker with the coordinator) ‑‑thread‑ratio (if using ‑‑run‑local‑worker with the coordinator)

© 2016 Adaptive Computing