in the same folder as the deployed
clcgridworker script, that is, the clcgridworker script within the folder specified in the Path to CLC Grid Worker field of the grid preset.
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 a temporary directory available from the grid nodes, overriding the defaults that would otherwise apply:
For each grid preset you created, you can create a
clcgridworker.vmoptions file within the folder you specified in the Path to CLC Grid Worker field. So for example, if you had two grid presets, you could set two quite different memory limits for the CLC Server java process.
This might be a useful idea in the case where you wished to provide two queues, one for tasks with low overheads, such as import jobs and trimming jobs in the case of CLC Genomics Server, and one for tasks with higher overheads, such as de novo assemblies or read mappings in the case of CLC Genomics Server.