and placing it in the same folder as the deployed
clcgridworker script, that is, within the folder specified in the Path to CLC Grid Worker field of the grid preset.
Options that may be of particular use for grid workers include:
-Xmx<value>Allows a limit to be set for memory use by the CLC Server java process.
-Djava.io.tmpdir=<path>Set the location where temporary files should be put.
-Dskip_lazytmp_cleanup=<boolean>When set to true,
-Dskip_lazytmp_cleanup=true, the grid worker will not attempt to clean up temporary data from previous analyses that, for whatever reason, were not cleared up previously. This option is intended for systems where temp areas for grid nodes are not local and the specified shared temp location is on a file system that does not support global file locking. As we highly recommend that temporary data areas are local, this option should rarely be of use.
For example, if a
clcgridworker.vmoptions was created, containing the following two lines, it would, for the CLC Grid Worker specified in a given preset, set memory limits for the CLC Server java process and set a temporary directory for the grid nodes, overriding defaults that would otherwise apply:
Each grid preset can have its own
clcgridworker.vmoptions file. So, for example, a different memory limit for the CLC Server java process could be specified for different presets. This could be useful where separate queues are used for low overheads tasks, such as import jobs and trimming jobs, and high overhead tasks, such as de novo assemblies or read mappings.