New SMP WUs
mmonnin
Centreville, VA
Lately all I have seen are the 1760 pointers but I remember some smaller ones back when I first started SMP.
I looked at my points for today and I had 2 WUs within the same update for 4,288 points and 2 1760 point WUs cant equal that ammount.
So I look on the WU lising page and I see one listed for 2539 points (p3060_BBA5_1). I dont seem to have any more but does anyone know if its new or how well it folds?
I looked at my points for today and I had 2 WUs within the same update for 4,288 points and 2 1760 point WUs cant equal that ammount.
So I look on the WU lising page and I see one listed for 2539 points (p3060_BBA5_1). I dont seem to have any more but does anyone know if its new or how well it folds?
0
Comments
p3062_lambda5_99sb - 1732 points - 1719 PPD Q66@3.24GHz
p3064_lambda5_2003 - 1753 points - 1713 PPD E66@3.15GHz
p3065_lambda5_99sb_big - 2144 points - 1510 PPD E66@3.15GHz
p3065_lambda5_99sb_big - 2144 points - 1599 PPD Q66@3.24GHz
The times were calculated with EM3 manually entering the time per % and point value. I usually get 2000-2100 PPD on each Q66 client and ~1900 on the E66 via the FahMon client so thats a nice point drop.
Not liking these new WU's...
These take a little longer and don't have quite the ppd. However, they may have other WUs that may be better point producers too- just haven't seen any yet.
http://foldingforum.org/viewtopic.php?f=8&t=1604
Scott
I'm not sure, Leo, but I've shut down SMP on my laptop a dozen different ways- from CTL-C to power-button shutdown (sometimes I simply don't have the time) and I've rarely lost a WU- and when I did I could not finger a shutdown reason. I've tried to peg this issue and the closest I could guess is network stability. These WUs ARE crazy flakey on a wireless system ... or almost any network where it has to find itself negotiating a new IP now and then. However, I'm not certain. My other guess is your overclocking, but heck- we almost all do that.
The latest SMP client is much more stable than the previous client. I almost never get a corrupted unit anymore at shut down, whether the shutdown is Ctrl-C, Windows shut down without stopping the clients, or even a hard restart with the power button or abrupt power interruption. Previously I did have problems with that. After I assigned static IPs to all the computers on the LAN, poof, that problem disappeared.
IMHO: This new client works hardly better (or worse) on a wireless network than ones they released months ago. It also craps out just about everytime I unplug my wired network cord. I think it has to do more with negotiating the IP address and not with the IP address itself because it craps out whether it negotiates the same IP address via DHCP or not.
I don't have the time or skill to debug all of FAH's bugs, otherwise I would have more exhaustively tested it and wrung out their source. So take it as speculation from what I've observed and read: I think this is an (perhaps THE major) unresolved problem with the SMP client- and it's plagued them since day one.
I actually don't remember WU corruption- perhaps that's because I started SMP months after many of you did (April last year) and have been folding inconsistently. My major SMP hangs have basically been: 1. Time restricted Beta updates and 2. Network drop-outs.
It seems like the FAH community is aware of it but, to date, there appears to be no fix.
Yeah- had my first EUE in months just this morning. On a 3064.
I'm pretty diligent about cleaning out my systems regularly- clean them all about the same time, and right now I've wound them down for the summer but can't monitor them regularly with my schedule. However, I'm not seeing a lot of abberation in the WUs I've had working recently- many of them 306xs- and my production is about dead-on with what I'd expect.
mmonnin- I'm half tempted to suggest your system/environment may need a more in-depth look-see.