Message boards :
Number crunching :
scheduler problem
Message board moderation
Author | Message |
---|---|
Send message Joined: 8 Jul 11 Posts: 1343 Credit: 515,898,796 RAC: 580,555 |
You may have noticed the server scheduler has been very fickle of late. I think part of the problem is related to how WUs have been segregated into batches (1 for normal app and 1 for GPU app). Since the GPU app has been relatively stable and has agreed with the CPU version on every WU tested (over 400), I have decided to remove the batch descriminator (this will open up the DS14x12 WUs to the GPU app). I now have over 100 GPU WUs. Interestingly enough they are all of the DS14x12 variety (batch 0) and all have a higher priority (due to accelerated retry mechanism). Ironically, I think this points to the root cause of the scheduler problem... I think this may have fixed the problem, at least for me it has. Please let me know if you still have problems receiving tasks. |
Send message Joined: 23 Jun 17 Posts: 5 Credit: 42,264,426 RAC: 0 |
Looks good so far. Thanks Eric |
Send message Joined: 7 Oct 11 Posts: 17 Credit: 17,442,841 RAC: 26,645 |
You may have noticed the server scheduler has been very fickle of late. Are there about equal numbers of both cpu and gpu workunits being created or you focusing on gpu workunits right now? I ask because I have some cpu cores that can't get work here right now and if I should be trying the gpu workunits instead. |
Send message Joined: 8 Jul 11 Posts: 1343 Credit: 515,898,796 RAC: 580,555 |
You may have noticed the server scheduler has been very fickle of late. The same WUs work on both cpu and gpu, so you should be able to get tasks for either. |
Send message Joined: 7 Oct 11 Posts: 17 Credit: 17,442,841 RAC: 26,645 |
You may have noticed the server scheduler has been very fickle of late. Thank you, it seems to be working now, your idea in the other thread about reissued workunits, was hopefully the problem. |