• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

TAS-member thread: October 2005

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
thanks for the heads up. i had two wu spinning there wheels 🙁

if that keeps up its back to folding.

i aborted them and then restarted the program and it seemed to get me some that work. i'll check them later.
 
I guess we'll just have to remember that it's still a beta client. Sean said that the main developer is usually pretty fast with dixing errors but he's in London right now. So I'll just give it a few days and try again.
 
Originally posted by: BlackMountainCow
I guess we'll just have to remember that it's still a beta client. Sean said that the main developer is usually pretty fast with dixing errors but he's in London right now. So I'll just give it a few days and try again.
Click to expand...


I am not sure if he is really back from vacation yet, but David Kim just started posting on the project forums again (concerning the errors). So hopefully the major issues will be resolved very quickly and we will have a new app in a day or so. 🙂
 
i'll keep running and watching. 😉

i have two machines, both x2's. each system currently runs 1 F@H and one rosetta.

perhaps coincidently but both times i got the "stuck" units it hit both machines at the same time.

well, in certainty, i guess i can only speak for yesterdays "stuck" units as i don't know how long the first episode had me spinning my wheels until i saw this issue posted.

just an fyi i guess. 🙂

lets keep climbing :thumbsup:
 
Thanks - thats is good goal, not only AMD-Users but also Phoenix Rising (in 5 607 days = 15 years, 4 month and 11 days? 😛 )
OK guys lets get crunching - more, very much more! 😀
 
Was this outage announced before the recent errors with the WUs happened or afterwards? I mean, is this outage due to a fix or just maintenance? I'd really like to do R@H again, but in the last 3 days every WU I tired (about 5 a day) failed on me at that freakin' 83% barrier.
 
This outage has been planned for quite some time (I have known about it for at least a week). It is a update of the server software so that R@H can use BOINC 5.x
I do not think there is any connection to the error in the WUs. 🙁 Since the R@H pages are down we can not check the progress on that problem until tomorrow. 🙁
 
And I have had my first two R@H WU errors.
The first was on the G4-minimac and the error code was completely different from all others I have seen. The WU stopped at 7½% and crunched on.
The second on my Athlon 64 3000+, the WU stopped @ 1% and it happened when the CPU-benchmark was run ... just as reported in R@H-forum some days ago. 🙁
I hope that this was not the start of a deluge of faulty WUs, but I fear that this may indeed be the case.
 
Originally posted by: mrwizer
I just love beta's 😉
Click to expand...


As a matter of fact, so do I (I mean really: we are at the edge of development).
Oh, BTW I have not had any errors on PCs for the last 8 hours. :thumbsup: :thumbsdown: :thumbsup:
However, my macs report 37 WUs "client error" and a code etc. in a row. Looked at the details and was surprized to see that on some WUs there were three computers reporting client errors while a fourth computer got a result correctly:

166737 9320 4 Oct 2005 7:39:28 UTC 5 Oct 2005 14:38:38 UTC Over Client error Computing 3,590.89 3.59 ---
178654 10758 5 Oct 2005 15:29:19 UTC 5 Oct 2005 15:29:28 UTC Over Client error Computing 0.00 0.00 ---
178811 8313 5 Oct 2005 16:58:16 UTC 5 Oct 2005 17:01:36 UTC Over Client error Computing 0.00 0.00 ---
179136 5895 5 Oct 2005 18:18:46 UTC 5 Oct 2005 23:46:35 UTC Over Success Done 10,384.97 24.72 24.72
Click to expand...

The successful CPUs were singlecore and "old" PIII or P4 below 2 GHz or older Athlons.
There were also some very fast single core CPUs running the failed WUs ... I have posted at R@H too - with more details.

I hope R@H crew will get that solved soon.
 
yeah, another folder or two would go a long way towards catching Baker.

phoenix will fall by the weekend 😛
 
so we're gaining about 1300 ppd on baker. about 2 months then.

maybe i'll convince one of my friends to crunch a bit on the rig i'm finishing for him 🙂 we need more crunchers! lol
 
TAS has quite some impact:
8 out of 14 crunchers are TAS-members.
The RAC for TAS is 2 426,31 credits, for the whole TA-team 3 203.93, i.e. TAS produces 75,73% of the RAC of the TeAm!
TAS has a total of 32 671,41 credits, compare that to the total of the TeAm: 52 763,41 credits. TAS has 61,9% of the TeAm's total!
That is a impact worthy of TAS! OK, OK, TAS had some 9700 credits before the start - but the development! We are only one week into the project: in that week TAS produced more than 23 000 credits.
Doesn't this look nice?

Before TAS started (one week ago) TeAm was in 11th position. Now the TeAm is in 6th. That's why TAS is a Rally-team! 😀
 
Once they get a few more issues resolved, I might throw a few more machines into the mix. 😉

And has anyone noticed yet what performs better on this project, Intel or AMD? I do not have enough machines on it to make a comparision.
 
Originally posted by: mrwizer
Once they get a few more issues resolved, I might throw a few more machines into the mix. 😉

And has anyone noticed yet what performs better on this project, Intel or AMD? I do not have enough machines on it to make a comparison.
Click to expand...

I could, but the time-line is not long enough for a reliable comparison, I'll look into this on Sunday, when I'll do the stats for TAS.
Don't you have some "old" computers (single CPU, without HT, single core) with at least 512 MByte RAM? Those have not given me any problems at all! (=no faulty WUs).
 
The problem I have seen with some of the machines (and others according to the project forums have had the same issues) is when you run a machine with more than one BOINC project. When the manager switches projects and takes Rosetta out of memory, it can sometimes fail. The macchine that is doing most of my work right now is only running Rosetta...

According to the forums, the way to fix this is to leave Rosetta in memory (which I do not have enough memory to spare on some of the machines) or only run one project, in this case Rosetta.
 
Yes, that is it; although I run at least 3 BIONC-projects on each computer, but I leave the prog in memory ... I hope they will fix a new update to the program soon!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top