-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
job.delay on torque clusters #121
Comments
The delay triggers a call to If you are able to switch over to batchtools, you can archive a delay before each submit by setting a hook in your cluster function constructor. Your config would then include something like cluster.functions = makeClusterFunctionsTorque([your stuff here], hooks = list(pre.submit = function(...) Sys.sleep(2)) Hope this helps. |
ok thanks alot
... and I can then post that @ batchtools... |
I'll answer this in the batchtools repo. |
Hi we're a couple of people using BatchJobs on our universitys torque cluster, thx alot for the package.
Now the support department would like us to reduce the speed of job submissions to like only one every 2 seconds or so. In submitJobs(reg,ids,job.delay), I can change the job.delay function, and it works well in an interactive session. However when the cluster function is torque, all jobs a submitted at a constant speed of 10 jobs per second, the job.delay function seems to be ignored completely.
How can I make BatchJobs delay the job submission?
printing from R linux session on torque cluster, job.delays is ignored and jobs are submitted really fast
printing from a interactive session (windows PC), there is a delay of of 2 seconds before each submission(and execution)
The text was updated successfully, but these errors were encountered: