• 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.

Rosetta@Home

I guess 10h is a bit high. I mean, yes, it depends on the PC, but even on my PIII 600 a WU usually doesn't need longer than 3 hours to jump to 10%, and that's the big WUs. If you've got one stuck for 10 hours, I'd say that's definitely a stuck one. 🙂
 
Huh, I wondered why my laptop was really dragging behind everything else. I had a 1% stuck in there for days apparently. Just deleted it.
 
i'm glad i havent seen any more. those were a PITA 🙁

good to see them on top of it though 🙂
 
I have not seen a single one....at least on the PC's I monitor. I will have to go and check my service systems manually.....arrrrggggg.
 
BadThad,

I recently figured out how to use BoincView in the Remote Procedure Call mode and it is fantastic. (anything you can do from boincmanager, you can do from a remote machine with boincview). well, that is if your remotes aren't hidden too deeply behind firewalls/security.

anyway, If you want to know how, PM me anytime

-Sid
 
The only one I ever had stuck was stuck at 80% that one time. Shot up from 70 PPD to 300 PPD after I fixed that too.
 
10 hours? That is a lot of wasted time.

I used to get a lot of these when Rosetta was still Beta and right afterwards. Although I have only had a few lately. Yet the other day I had a machine stuck at something other than 1% (forgot which %) 🙁
 
OMG after I posted that I checked at wouldn't you know it, 2 stuck WU's 🙁

It seems they might not actually be stuck though. After 45 minutes one shot to 10%, then up to 20% a moment later. The other stuck at 1% for an hour so I just suspended, let another WU start, and put it at the back of the line, to see if it will work later. I just wish it were more accurate on how the WU is going. I have no idea whether it really is stuck or not.
 
I have no idea what anything means in regards to this projects interface. I installed it & joined three days later. I hope I have everything set correctly. That bubble that pops when the curser rolls over it is pretty annoying.
 
ya know, this evening I've been trying to pay some attention and I'm seeing similar things. Most of my WUs take ~30 or 40 minutes, but I notices one at almost 2 hours (80%) then in the course of about 5 minutes it finished!

I'm thinking this is a false alarm and just their progress indicators are .... wierd :roll:

I think I'm not going to touch anything unless I see 3 or 4 hours on it. (that one that took 2+ hours gave me lots of points (~50 or just less if I remember right.)

I watched another one later that was at 10% after (literally) 1 minute, but had a normal-ish completion time of 37 minutes.

I'll keep watching, but I'm not too concerned now
 
For your info:

The WUs of Rosetta usually work faster in the first 80% and then slow down for the last 20%. The science that is done changes in the alst 20% and needs more time.

The time also heavily depends on the type of WU. Right now, most WUs contain a string like "len10" which means lenght 10. But there are also WUs "len20" and and very few "len30". That means, they take twice or thrice as much time as the len10 ones. Thus, they'll appear stuck on 1% for a longer time. As far as the "topology sample" WUs are concerned, I guess they're all the same lenght, but they don't really tell.

On my X2-4400+ some of the len20 need as long as an 1:24h to pass to the 10% mark. Then again, they appear to be stuck at 80%, but they aren't. I haven't heard or read about any WUs stuck at any other mark than the 1% one. So, once you're past that, you should be safe.

I know, it's a difficult decision, but recently a lot of WUs get killed too early, altough they weren't stuck but just needed more time. Just check the name of the WU and the "lenXX" string. That can give you a rough estimation.

I just asked on the R@H forums if the gfx would actually tell you if a WU is stuck by not moving and whiggling any more. Stay tuned, I'll further investigate into that. Should anyone of you have a stuck WU, please open the visuals and see what it does.

🙂
 
Macs are a different matter. Have not had any "stuck" WUs for a very long time, but I have had many (approx 70 - 80) "computation error"-WUs. That has been solved (I now run without those errors) but I thought the time the WUs took was terrible: 11 - 12 hours on a G5-processor @2.0GHz - until I got some "normal" WUs, which crunched in 6 - 5 - 4 hours. Now I have a WU which is - after 18 minutes - @ 40%. I estimate that the WU will take som 4 hours to finish ...
I think Rosetta@Home is running quite a few different experiments now - and that they are adjusting the WUs accordingly. 🙂

Especially the proteins starting with the string "1ogw__topology..." take tremendously long times (39000 - 45000 seconds, i.e. 10 - 13 hours, OTOH they also give 110 - 125 credits ... 😀

I have quite a few of those downloadad in my buffer, 🙂 especially since I can crunch 2 at a time ... the Mac does some 350 - 450 credits a day. which is not too bad 😉
 
It looks like the gfx are the key to the problem with stuck WUs. If you think you have a stuck WU but aren't sure, check the gfx. If they're stuck, too, no more whiggling and moving and just the timer counting, then you have a stuck WU. Watch the gfx for 5 minutes. If nothing moves, then close the whole BOINC. Restart it and turn on the gfx for that WU again. Most likely it'll work now. If not, then abort the WU.

🙂

 
Thank You Sir!

Of course, since I posted this, I haven't had a difficulty all day.... Thanks to you I'll know what to do if it comes up again!

-Sid

Cold :beer: :beer: and a warm :cookie: for BMC
 
Back
Top