Message boards :
Multicore CPUs :
Error with more than 32 threads
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 4 Oct 09 Posts: 6 Credit: 110,801,812 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
I got this error: Fatal error: 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.In that case, the maximum number of threads should be limited either in the application or the server side. |
|
Send message Joined: 2 Jan 09 Posts: 303 Credit: 7,387,800,090 RAC: 521 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. |
|
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. |
MJHSend message Joined: 12 Nov 07 Posts: 696 Credit: 27,266,655 RAC: 0 Level ![]() Scientific publications ![]()
|
Limited to 32 now. |
|
Send message Joined: 2 Jan 09 Posts: 303 Credit: 7,387,800,090 RAC: 521 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 |
|
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. |
|
Send message Joined: 2 Jan 09 Posts: 303 Credit: 7,387,800,090 RAC: 521 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
Limited to 32 now. Ahhh, thanks for adjusting it then! |
©2026 Universitat Pompeu Fabra