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

F@H slow WU's --Solved--Stanford has killed this WU

Pokey

Platinum Member
I have picked up some really slooooooow WU's. P6013 = 69ppd on a quad core SMP2, and P6701 = 244 ppd on a dual core. No solutions mentioned that I could find on Stanford's forum.

I tried to clean house and restart the client but it keeps getting the P6013 WU.

Anyone know anything more about this??
 
Last edited:
Those are WUs that get a bonus with early completion.

Are you using HFM to monitor? It supposedly calculates the bonus.
 
I had one that was 101 ppd, on a cpu that normally gets 5000 (even with the bonus) something is up with these. 4 days to complete ??

Don't hold me to it, but the same CPU is getting 6500 ppd after the 101 ppd one finished after 3 days. I didn;t even touch the box.
 
Yes GLeeM, I'm using HFM.net to monitor, and love it. After years of FAHMON, wish I'd have picked up on it sooner. It does not seem to be figuring a bonus...................

Mark, I guess I'll let them ride and see what happens. I just hate to sit three days looking at 69 PPD when I'm not use to it......... LOL

Hey, it's all for science right.........??
 
I got one of those this morning, I thought something was wrong because it's a brand new rig and I just started up the GPU3 (on an ATI 5770) so i deleted the queue and got a new WU. If I get another I'll let it run to completion and see if I get a bonus.
 
Remember the SMP2 WU shortage recently? Remember what Standford says about "cherry picking" WUs, that it causes a shortage? Maybe it would be best just to let it calculate..
 
Remember the SMP2 WU shortage recently? Remember what Standford says about "cherry picking" WUs, that it causes a shortage? Maybe it would be best just to let it calculate..

You may be right, but because of the beta nature of the project and Stanford's reputation for putting out a "bad" (my word) work unit from time to time, it is just force of habit with me to clean house as a first reaction. Not saying it's right, just saying.............
 
I have picked up some really slooooooow WU's. P6013 = 69ppd on a quad core SMP2, and P6701 = 244 ppd on a dual core. No solutions mentioned that I could find on Stanford's forum.

I tried to clean house and restart the client but it keeps getting the P6013 WU.

Anyone know anything more about this??

Some of the 6013 take 10x longer than normal to complete. Stanford is looking into this. http://foldingforum.org/viewtopic.php?f=19&t=14966 http://foldingforum.org/viewtopic.php?f=19&t=14957

There was an issue with the bonus points for 6701 reported to Stanford last week, so hopefully that will be corrected. http://foldingforum.org/viewtopic.php?f=58&t=14911
 
Am I right in reading that I have to complete 10 of these things with 80% early completion time before I start to get the bonus for them?
 
Yes.

I've never heard of the slow 6013s, but there seem to be a lot of the 6701s, maybe to make up for a decreasing amount of work?
 
I find it interesting how so many people have problems with this WU and my completely stock i7 -920 does them at under 4m/frame. Althought it's not exactly the same, mine is 6013 (Run 0, Clone 168, Gen 144). The ones that take me the longest are the 6701 (Run 82 Clone 23, Gen 4). Right now it's taking 10:22 per frame.
 
I find it interesting how so many people have problems with this WU and my completely stock i7 -920 does them at under 4m/frame. Althought it's not exactly the same, mine is 6013 (Run 0, Clone 168, Gen 144). The ones that take me the longest are the 6701 (Run 82 Clone 23, Gen 4). Right now it's taking 10:22 per frame.

Many of the 6013 WUs do not have any issues.
 
Back
Top