You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the global.cylc, we have our share and work directories on lustre, which are symlinked into our workflows area. Typically, we access those locations using things like CYLC_TASK_WORK_DIR and ROSE_DATAC - but they go through the symoblic link. Under low traffic, that is fine, but, we have shown under high traffic this can cause problems and it is less load on metadata servers to use the real path. Someone explained it to me a while ago, but I've forgotten what goes on each time a symbolic link is traversed.
Proposed Solution
When a workflow is installed, it obviously knows that real path as it sets the symlinks up. I would like those variables made available directly in a job script so we can avoid traversing the symbolic links when scripting. I think the symlinks are useful for navigating easily in interactive mode, but from an efficiency perspective, not using them inside a script is better.
The text was updated successfully, but these errors were encountered:
Problem
In the global.cylc, we have our
share
andwork
directories on lustre, which are symlinked into our workflows area. Typically, we access those locations using things likeCYLC_TASK_WORK_DIR
andROSE_DATAC
- but they go through the symoblic link. Under low traffic, that is fine, but, we have shown under high traffic this can cause problems and it is less load on metadata servers to use the real path. Someone explained it to me a while ago, but I've forgotten what goes on each time a symbolic link is traversed.Proposed Solution
When a workflow is installed, it obviously knows that real path as it sets the symlinks up. I would like those variables made available directly in a job script so we can avoid traversing the symbolic links when scripting. I think the symlinks are useful for navigating easily in interactive mode, but from an efficiency perspective, not using them inside a script is better.
The text was updated successfully, but these errors were encountered: