| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 8
|
|
| Author |
|
|
Dougga
Cruncher Joined: Apr 17, 2007 Post Count: 7 Status: Offline Project Badges:
|
I have several computers running WCG via boinc. In reviewing the performance of the systems I find that AMD64 processors are returning very very few results even though they are more powerful processors by an order of magnitude relative to my older machines.
I can find no reson for this and have found computation errors in the logs but nothing that indicates the magnitude of the failures. It seems that nearly all results are failing. Two questions: 1) Are AMD chips not supported by this effort. I will move my cpu's to other groups if so. I will not support engineers who do not support AMD adequately. [Given the history of Wintel's marketing methods, I am suspicious of such situations] 2) If certain machines show 90+% error rates, why doesn't World Community Grid make this clear to the user? Wouldn't it be in everybody's best interest to come forth with the information that we're wasting electricity and filling the atmosphere with greenhouse gases for naught? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi
Don't have failure issues here with my AMD machines. Of course how long WU's take largely depends on cpu speed etc etc. Are you overclocking?.....If so is the overclock stable? Perhaps you are having stability issues with your hardware. Have you tried running the likes of prime 95 and memtest? Hope you get to the bottom of your WU issues. |
||
|
|
retsof
Former Community Advisor USA Joined: Jul 31, 2005 Post Count: 6824 Status: Offline Project Badges:
|
In My Grid, look at your results status. A bunch of invalids indicate the problems (excessive overclocking or bad memory) in the previous message. AMD64 in general should produce MORE results due to a good floating point computation. I have 3 AMD64 sending 4 to 8 results per day EACH on FAAH. They are running 32 bit WinXP. Vista has a few different issues. Two are 2.4GHz. One is a newer 2.0GHz overclocked to 2.4GHz. No problems, and it runs cooler than the others. If overclocking is turned too high, the invalids start to show up.
----------------------------------------Incompatible memory sticks can cause invalids. When adding another, it took three tries, testing with memtest86+ each time, to find a set that worked together. You might also try a different project to see whether that makes any difference, but it shouldn't. A faster computer than 1.0GHz should run anything here. Do you have ENOUGH memory on the system?
SUPPORT ADVISOR
----------------------------------------Work+GPU i7 8700 12threads School i7 4770 8threads Default+GPU Ryzen 7 3700X 16threads Ryzen 7 3800X 16 threads Ryzen 9 3900X 24threads Home i7 3540M 4threads50% [Edit 3 times, last edit by retsof at Sep 23, 2007 10:13:03 PM] |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7850 Status: Offline Project Badges:
|
Post some of the BOINC messages that show what the computers are doing. That should help shed some more light on the subject. Include info on OS, memory, etc.
----------------------------------------Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
Dougga
Cruncher Joined: Apr 17, 2007 Post Count: 7 Status: Offline Project Badges:
|
In the My Results section I see that most work units error out.
Here are the errors: No such file or directory They all seem to be the same error regarding the lack of a file or directory. Curious. Anyone have any ideas? Result Log <core_client_version>5.4.11</core_client_version> <message> process exited with code 2 (0x2) </message> <stderr_txt> 2007-09-22 08:59:10 [World Community Grid] Process creation (../../projects/www.worldcommunitygrid.org/wcg_faah_autodock_5.41_i686-pc-linux-gnu) failed: Error -1 execv: No such file or directory </stderr_txt> Result Log <core_client_version>5.4.11</core_client_version> <message> process exited with code 2 (0x2) </message> <stderr_txt> 2007-09-22 08:57:53 [World Community Grid] Process creation (../../projects/www.worldcommunitygrid.org/wcg_faah_autodock_5.41_i686-pc-linux-gnu) failed: Error -1 execv: No such file or directory </stderr_txt> Result Log <core_client_version>5.4.11</core_client_version> <message> process exited with code 2 (0x2) </message> <stderr_txt> 2007-09-22 03:38:24 [World Community Grid] Process creation (../../projects/www.worldcommunitygrid.org/wcg_faah_autodock_5.41_i686-pc-linux-gnu) failed: Error -1 execv: No such file or directory </stderr_txt> |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello Dougga,
----------------------------------------All the examples shown are FAAH errors. Do other projects also show errors on these computers? Do these computers ever return valid FAAH results? Is there a distinct set of projects that always fail or always succeed on these computers? Have you rebooted these computers? Have you ever detached these computers from WCG, then reattached? Lawrence Added: Incidentally, isn't i686-pc-linux-gnu 32-bit Linux, not 64-bit Linux? When you say AMD64, just what do you imply about your OS? It can run 32-bit Linux applications, can't it? [Edit 1 times, last edit by Former Member at Sep 24, 2007 7:48:47 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I notice you are using BOINC 5.4.11. Where did you get it from?
You will get best results with the 32bit Linux release. |
||
|
|
jal2
Senior Cruncher USA Joined: Apr 28, 2007 Post Count: 422 Status: Offline Project Badges:
|
I had a similar lack of results problem after upgrading my Athlon 64 to openSuSE 64, and finally tracked it down to the beagled-helper task taking over the machine. This task is supposed to run at idle-process level, but apparently has an issue with unknown file types, and will start grabbing all of the CPU. The recommendation seems to be to either disable the active search option in the user preferences, or to uninstall this part of the beagle package until the developers can fix the problem.
---------------------------------------- |
||
|
|
|