- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I am facing an issue with the time taken by DevCloud to run a job.
The time taken to run a job is easily 7 times more than it used to take a week back for unchanged code.
Also, there was no change in the run time when the nodes were allocated or not.
This might be because of the node allocation issue or something else related to node network.
It would be very helpful if you can check this and revert back as soon as possible.
For your information,
The command-line which I used to allocate node is
qsub -I -l nodes=4:ppn=2
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Thanks for posting in Intel Forums. We will check with the concerned team and get back to you.
Regards,
Alekhya Vemuri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Does the issue still persist? If yes, please try submitting the job at different times and check whether the issue still exists. Please let us know the same
Regards,
Alekhya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Yes, the issue still persists and keeps existing for a run at different times.
Please look at the issue again and revert me back.
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
We will inform the admin team regarding this and get back to you soon with an update.
Regards,
Alekhya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
The issue has been resolved from our side. We don't find any delay while running a job in DevCloud. Please check the same and let us know.
Thanks,
Alekhya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Thank you for your effort, but as of now, I don't find time gain while running the job with unchanged code.
It is taking the same time as it used to take earlier i.e 7 times more than the usual case.
I will do a check again and will confirm it by tomorrow.
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Please give us an update regarding this issue.
Thanks,
Alekhya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Apologize for the delay in updating.
I don't find any improvements, the issue is still persisting.
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
We're working with the admin team regarding this issue. We'll get back to you soon.
Thanks,
Alekhya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
We apologize for the delay. According to the response we got from the DevCloud team, DevCloud does not make any assurance for how long it takes for a resource to be allocated to a job. A job can be configured to be triggered automatically after another job completes successfully. So, It completely depends on the nodes available at that particular time so that they can get allocated to a new job.
Thanks,
Alekhya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Could you please give us an update regarding this issue?
Regards,
Alekhya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
We assume that your issue is resolved. If you need any additional information, please post a new question as this thread will no longer be monitored.
Regards,
Alekhya

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page