Frequently Asked Questions and Troubleshooting Tips

The wrapper vwn (alias for vw -N) avoids communication with vovserver. An example is shown below:

% wx run -wrapper vwn sleep 0

If analyzing what causes wait time in the workload, the wait reason analysis can be disabled as shown below:

# In policy.tcl
set config(enableWaitReasons) 0

Wait time analysis can then be re-enable as needed as shown below:

% wx cmd vovsh -x 'vtk_server_config enableWaitReasons 1'

### collect some data for a few minutes, then

% wx cmd vovsh -x 'vtk_server_config enableWaitReasons 0'

Disabling file access is mostly a high-reliability option. By disabling file access, the vovserver never looks at any of the files in the user workspaces, which avoids the risk of disk slowness or disk unavailability. An example is shown below:

% wx cmd vovsh -x 'vtk_server_config disablefileaccess 2'

Notify clients, clients that are tapping the event stream from vovserver (such as wx gui, voveventmon or wx run -wl), are updated immediately in the inner loop of the scheduler. If the environment includes hundreds of such clients, it may be beneficial to slow down the update rate by setting the parameter notifySkip. The default value is 0: no skip. Typically, the more events that take place, the more events that can be skipped without notice. For example, if several events are taking place, setting notifySkip to 100, fewer updates may not be noticed. If the number of events is small, a one-second delay may be noticed in some updates of the GUI. skipped without notice.