Taskers on Windows
Accelerator can dispatch jobs to taskers running on Windows hosts. Starting the taskers on Windows hosts, however, is less automated than on UNIX hosts.
To prepare the Windows host:
Configure Taskers on Windows
View new features for Accelerator 2021.2.0.
Discover the available Altair Accelerator guides.
Discover Accelerator functionality with interactive tutorials.
Basic tasks in Accelerator, including submitting jobs, tracking job information, and analyzing and solving common problems.
Configure and manage the use of Accelerator after it is installed.
Accelerator documentation is available in HTML and PDF format.
Accelerator has two main commands, nc and ncmgr.
This daemon vovfilerd replaces older daemons like vovisilond, vovnetappd and vovregulatord. Also the utility vovfiler_setup is no longer needed. The visualization of the filer information is now done either via the vovfilerd.cgi page or via the utility vovfilerdgui.
A tasker is a VOV client that provides computing resources, specifically CPU cycles, to the vovserver.
A normal vovtasker has the privileges and limitations of the account in which it runs. When a normal vovtasker executes a command, the effect is the same as when the vovtasker's owner runs the command.
The taskers.tcl file describes the taskers for a project.
There are many options that can be used with vtk_tasker_define and vtk_tasker_set_default.
A tasker is characterized by several attributes. These attributes are controllable by means of the command line arguments to the vovtasker binary as well as by means of the procedure vtk_tasker_define in the taskers.tcl configuration file for a VOV project.
A tasker list is a named, ordered list of taskers. Tasker lists can be used to enhance performance or restrict usage.
The resources of a tasker include SLOTS, SLOTSTOTAL, CORES and CORESTOTAL.
By default, the vovtasker does not perform many health checks. If the jobs can be executed successfully, that is normally enough of a check.
For cases where the vovtaskers are started by submitting the binary to a separate batch queue system such as LSF or SGE, the system administrator
may decide to use vovagent
, which is a special copy of the vovtasker
binary.
vovtasker continuously logs 1 minute, 5 minute and 10 minute load averages of the machine where the tasker is running. Tasker load reports are available on the Tasker Load page.
Time-variant taskers resources can be configured using Tcl. Any procedure can be defined in the namespace VovResources
and then used to compute the resource list.
vovtaskers also support SGE style load sensors. Use option -L in vovtasker/vovtaskerroot to define the command line for the load sensor.
Accelerator stores historical information about jobs in a relational database. As of version 2015.09, the database is fully integrated and managed as part of Accelerator. This section provides an overview of the components that run and manage the database.
Preemption is the process of reserving or revoking resources from other jobs in order to help "important jobs" finish quickly.
Altair Accelerator includes a subsystem for managing computing resources. This allows the design team to factor in various constraints regarding hardware and software resources, as well as site policy constraints.
To ensure the correct and repeatable behavior of the tools, the environment must be controlled. This chapter explains how VOV supports multiple reusable environments.
If a server crashes suddenly, VOV has the capability to start a replacement server on a pre-selected host. This capability requires that the pre-selected host is configured as a failover server.
This section provides instructions to change the software version on which Accelerator runs.
This chapter provides information about deprecated features that are still supported. This information is provided should you see older commands in use after a software upgrade or migrating to a newer Accelerator.
Configure and manage the use of Accelerator after it is installed.
Accelerator can dispatch jobs to taskers running on Windows hosts. Starting the taskers on Windows hosts, however, is less automated than on UNIX hosts.
To prepare the Windows host:
f:\rtda\<version>
. Enter the
location depending on your network setup.
cmd
shell . Initialize it by executing the
vovinit.bat script that is in the installation
directory under win64/bat.
% f:\rtda\<version>\win64\bat\vovinit.bat
The
vovinit.bat
file adds the Altair Accelerator commands to the PATH and sets other environment variables used by the
software.
cmd /k f:\rtda\<version>\win64\bat\vovinit.bat
Refer to the Windows documentation to learn how you can add a shortcut to the desktop.
% vovtsd -user vncadmin
where vncadmin
should be replaced by the login name of the
Accelerator administrator who is running the Accelerator
vovserver.
vnc.swd/taskers.tcl
.
% ncmgr reset -taskers
Copyright (c) 1994-2021. Altair Engineering, Inc. All Rights Reserved. Contains trade secrets of Altair Engineering, Inc. Copyright notice does not imply publication.