Message boards : Multicore CPUs : Error with more than 32 threads
| Author | Message |
|---|---|
|
Sebastian M. Bobrecki Send message Joined: 4 Oct 09 Posts: 6 Credit: 110,801,812 RAC: 0 Level  Scientific publications     | |
|
I got this error: Fatal error: In that case, the maximum number of threads should be limited either in the application or the server side.64 OpenMP threads were requested. Since the non-bonded force buffer reduction is prohibitively slow with more than 32 threads, we do not allow this. Use 32 or less OpenMP threads. | |
ID: 39114 | Rating: 0 | rate:
 /   Reply
Quote
| |
|
mikey Send message Joined: 2 Jan 09 Posts: 297 Credit: 6,230,759,241 RAC: 29,150,608 Level  Scientific publications   | |
I got this error: To make this work on your machine I think you could limit the number of cpu's to 50% on that machine, get work, set it no new work, and then reset the cpu's back to 100%. This should force the cpu units to ONLY use the cpu's it saw when the units were downloaded, yet let you run other tasks on the other cores. It will be a pain to remember the steps every time you need more work, but after a few times it could become routine. Setting the limit WITHIN the app though would be a MUCH better option, but that is the projects job and nothing a cruncher can do about it. | |
| ID: 39117 | Rating: 0 | rate:
/ Reply
Quote
| |
|
Sebastian M. Bobrecki Send message Joined: 4 Oct 09 Posts: 6 Credit: 110,801,812 RAC: 0 Level Scientific publications | |
To make this work on your machine I think you could limit the number of cpu's to 50% on that machine, get work, set it no new work, and then reset the cpu's back to 100%.Yes, I already figured it out. This should force the cpu units to ONLY use the cpu's it saw when the units were downloaded, yet let you run other tasks on the other cores. It will be a pain to remember the steps every time you need more work, but after a few times it could become routine.In my case, it didn't work that way. I mean, when I set cpu number back to 100%, other tasks didn't start. Setting the limit WITHIN the app though would be a MUCH better option, but that is the projects job and nothing a cruncher can do about it.I think that setting this in application, or perhaps somehow in project server configuration is the only sensible solution. | |
| ID: 39118 | Rating: 0 | rate:
/ Reply
Quote
| |
 MJHProject administrator Project developer Project scientist Send message Joined: 12 Nov 07 Posts: 696 Credit: 27,266,655 RAC: 0 Level  Scientific publications | |
|
Limited to 32 now. | |
| ID: 39124 | Rating: 0 | rate:
/ Reply
Quote
| |
|
mikey Send message Joined: 2 Jan 09 Posts: 297 Credit: 6,230,759,241 RAC: 29,150,608 Level Scientific publications | |
Limited to 32 now. Does this affect what we are talking about here: "Increasing the maximum number of coprocessor devices to 64." That is one of the changes in the latest version of Boinc that was just released for testing. http://boinc.berkeley.edu/dev/forum_thread.php?id=8649 | |
| ID: 39137 | Rating: 0 | rate:
/ Reply
Quote
| |
|
Sebastian M. Bobrecki Send message Joined: 4 Oct 09 Posts: 6 Credit: 110,801,812 RAC: 0 Level Scientific publications | |
Limited to 32 now. No, it is about specific feature of the GROMACS application which is used by GPUGRID for this tasks. | |
| ID: 39138 | Rating: 0 | rate:
/ Reply
Quote
| |
|
mikey Send message Joined: 2 Jan 09 Posts: 297 Credit: 6,230,759,241 RAC: 29,150,608 Level Scientific publications | |
Limited to 32 now. Ahhh, thanks for adjusting it then! | |
| ID: 39144 | Rating: 0 | rate:
/ Reply
Quote
| |
Message boards : Multicore CPUs : Error with more than 32 threads
