• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Big Unit moves in!

Bodega said:
heh.. just got one on the other cpu too :rolleyes:

They must have become more popular. All my non-borged boxen are now owned by the 600 pointer. I guess I won't have any points for a day or so.
 
No 600 pointers for me yet. I have only managed to get a few 300 pointers. One terminated early and I got credit for the work that was done. Another processed just fine and was sent back. I was working on another one but my system ended up somehow "messing up". I have no clue what happened to it. A reboot fixed the problem for now. This is the second time this has happened and I'm not sure what is going on. I have had to format and re-install twice lately for various reasons, although not because of stability problems. Well, it ended killing all the work I had done on the protein and started over. Talk about annoying.

 
I just got a 600 point WU this morning on one of my Sempron 2200+ rigs. I have it OC'd about 150 Mhz to bring it to 1.65 GHz, and it is running a 52:53 frame time. It is crunching protein p1134_RIBO_FSpeptide_EXT, if anyone wanted to compare their progress. Calculated out, it is 6.8 PpH, and is going to take about 3.5 days to complete. This is a dedicated folding rig, too, so the only hit it takes is EM3 a few times a day to check progress.
 
ARRGH! Just screwed myself out of my one and only 600. It was already 1/3 done and I decided to overclock the system to give it a little kick. Kick it it did, right out of the machine :mad:

Code:
[14:03:02] Completed 80000 out of 250000 steps  (32)
[14:36:10] Quit 101 - Fatal error: NaN detected: (ener[13])
[14:36:10] 
[14:36:10] Simulation instability has been encountered. The run has entered a
[14:36:10]   state from which no further progress can be made.
[14:36:10] If you often see other project units terminating early like this
[14:36:10]   too, you may wish to check the stability of your computer (issues
[14:36:10]   such as high temperature, overclocking, etc.).
[14:36:10] Going to send back what have done.
[14:36:10] logfile size: 8660
[14:36:10] - Writing 9223 bytes of core data to disk...
[14:36:10]   ... Done.
[14:36:10] 
[14:36:10] Folding@home Core Shutdown: EARLY_UNIT_END
[14:36:14] CoreStatus = 72 (114)
[14:36:14] Sending work to server


[14:36:14] + Attempting to send results
[14:36:14] + Results successfully sent
[14:36:14] Thank you for your contribution to Folding@Home.
[14:36:18] - Preparing to get new work unit...
[14:36:18] + Attempting to get work packet

u_BaitFish
 
Mine are pumping at 168-248 ppd. So far I have ones on:
1.48Ghz Opteron 240
1.6Ghz Athlon 2100+
1.6Ghz Mobile Athlon 3000+ "Dothan"
1.8Ghz Pentium M
2.1Ghz Athlon 2400+
2.3 Ghz Mobile Athlon 2500+

Frequency noted is actual "overclocked" frequency of CPU.
 
Some more numbers.
My dual Athlon MP's are folding these big packet work units at around 3.3 - 3.6 Points per Hour per Ghz
My dual Opterons are folding these big packet work units at around 4 - 4.2 Points per Hour per Ghz.
Stanford benchs at 1.63 Point per Hour per Ghz but you do get a bonus for running them.
From their point / time it looks like the bonus is a 100% increase in points so 3.3 PpHpG is the speed you should run them.
So my Athlons are running at the right speed and my Opteron are running around 25% faster.

Luck.......... :D
u=Tigerbiten.gif
 
two more today...

2.55 xeon
2.55 xeon
1.8 xeon
2.8b p4

ill let you guys know how long each one takes although the timing on the 2.55ghz xeons might be a bit off since its my main rig... originally it was projecting around 70 hours each. on the 1.8 its projecting about 100 hours and on the 2.8 around 60 hours. ;)
 
I got 12 of these buggers right now.

Had a circuit blow, lost ~14 hours of folding time across 10 boxen. That hurts. I don't quite know why it took 3 days for this device to blow.... Guess I should have spent more than 6 seconds on power management...

Bait-Fish- Yea know the feeling. I kinda chickened out on one of my OC'd boxen after if barfed a WU. So then I OC'd the heck out of a slower boxen...

Marty
 
Well,

So far Pentium M seems to be winning on my systems with the 600 Pointers:

31 Minutes a Step for a 1.8Ghz Pentium M (11.6 PpH or 6.44 PpHpGhz) 1135_RIBO_FSpeptide_HEL (1135 Run100, Clone 23, Gen 0)
vs
35.5 Minutes a Step for a 2.31Ghz Athlon XP (10.1 PpH or 4.39PpHpGhz) p1135_RIBO_FSpeptide_HEL (1135 Run11, Clone 0, Gen 5)
vs
45.75 Minutes a Step for a 1.44Ghz Opteron (7.87 PpH or 5.46PpHpGhz) P1134_RIBO_FSpeptide_EXT (1134 Run 91, Clone 10, Gen 0)
vs
41 Minutes a Step for a 2.1Ghz Athlon XP (8.76 PpH or 4.17PpHpGhz)
P1135_RIBO_FSpeptide_HEL
vs
118 Minutes a Sep for a 1.0Ghz Athlon (3.05 PpH or 3.05PpHpGhz)
P1141_RIBO_FSpeptide_HEL_nospring (1141 Run 120,Clone 11,Gen 1)

Now, of course, These are all different WU's so that could be some the deviation. But a big win for the Pentium M.

Edit: to add protein information.
edit2: Added Athlon 1Ghz Information and Athlon XP 2.1Ghz information
 
Hito Bahadur said:
Well,

So far Pentium M seems to be winning on my systems with the 600 Pointers:

31 Minutes a Step for a 1.8Ghz Pentium M (11.6 PpH or 6.44 PpHpGhz)
vs
35.5 Minutes a Step for a 2.31Ghz Athlon XP (10.1 PpH or 4.39PpHpGhz)
vs
45.75 Minutes a Step for a 1.44Ghz Opteron (7.87 PpH or 5.46PpHpGhz)

Now, of course, These are all different WU's so that could be some the deviation. But a big win for the Pentium M.
How close are the project numbers? I think closer numbers are more related projects...
 
unhappy_mage said:
How close are the project numbers? I think closer numbers are more related projects...


See edited post. It looks like they are definately all different to some degree. Still, interesting stats.
 
Bait-Fish said:
ARRGH! Just screwed myself out of my one and only 600. It was already 1/3 done and I decided to overclock the system to give it a little kick. Kick it it did, right out of the machine :mad:

Code:
[14:03:02] Completed 80000 out of 250000 steps  (32)
[14:36:10] Quit 101 - Fatal error: NaN detected: (ener[13])
[14:36:10] 
[14:36:10] Simulation instability has been encountered. The run has entered a
[14:36:10]   state from which no further progress can be made.
[14:36:10] If you often see other project units terminating early like this
[14:36:10]   too, you may wish to check the stability of your computer (issues
[14:36:10]   such as high temperature, overclocking, etc.).
[14:36:10] Going to send back what have done.
[14:36:10] logfile size: 8660
[14:36:10] - Writing 9223 bytes of core data to disk...
[14:36:10]   ... Done.
[14:36:10] 
[14:36:10] Folding@home Core Shutdown: EARLY_UNIT_END
[14:36:14] CoreStatus = 72 (114)
[14:36:14] Sending work to server


[14:36:14] + Attempting to send results
[14:36:14] + Results successfully sent
[14:36:14] Thank you for your contribution to Folding@Home.
[14:36:18] - Preparing to get new work unit...
[14:36:18] + Attempting to get work packet
It's been a steady stream of these since I first posted. Looking back thru my logs, I see the same thing happen to one of my 600s. The WU before and after it completed, nothing done to the boxen itself, so I'd not sweat it too much...

I love the virtual "THUD!" I hear when one of these things hits the stats page. :D
 
Oooh how exciting I just got my first one of these!!!! :D
A new protien for the stats in EMIII.
Still waiting for a frame to complete to see how long it will take.


 
Mayhem33 said:
Oooh how exciting I just got my first one of these!!!! :D
A new protien for the stats in EMIII.
Still waiting for a frame to complete to see how long it will take.



It takes a lot longer to get instant gratification. I may go all day tomorrow without any points because of 600 pointers. :( But they are neat.
 
I have gotten now about 10+ of these honkers, and running consistently 32 minutes per frame on my Athlon64 3200+ 1MB L2 and 50 minutes per frame on my AthlonXP 2400+ stock speed. It seems the different protiens are not really affecting the PPH. Of course, I could just be talking out my butt and know nothing. Which is probably true.
 
Got 18 of these bastards now.... Gonna be taking one major dump soon... :eek:

instant gratification- yea no kidding... things are slow enough w/o these toilet cloggers...

Marty
 
I just lost one today. The Laptop kicked it for some other reason and I lost a 70% complete unit..... losing 400 points like that sucks. :(
 
Hito Bahadur said:
I just lost one today. The Laptop kicked it for some other reason and I lost a 70% complete unit..... losing 400 points like that sucks. :(

Are you sure it's lost? A lot of times when a work unit ends early, it will send the results that you have back. In that case you get credit for the work you did.

I had a 300 pointer die on me for no reason and ended up getting 120 points credit for what was sent back.

 
SmokeRngs said:
Are you sure it's lost? A lot of times when a work unit ends early, it will send the results that you have back. In that case you get credit for the work you did.

I had a 300 pointer die on me for no reason and ended up getting 120 points credit for what was sent back.


It started the unit over because the check failed..... so the work is lost, not the WU itself.
 
Damn, I like these 600 pointers. After finishing up a 302 pointer, my system got p1135_RIBO_FSpeptide_HEL. So far it's burning through frames at 30 min 40 sec with the rig in my sig. It should take about 51 hours to complete. That's about 4.7 pts/Ghz/hour. It's nice to see.

 
Buckus said:
about 32 min per step on my rig in my signature. About 50 minutes per step on Athlon 2400+ at stock speed, 768 MB RAM.

Is that 2400+ a Sempron?
 
W00t: With 8 CPUs and over 11Ghz of computers outputting and over 900+ points per 24hr average, I managed to score zero points on the 5th :)

Hopefully tomorrow is better. Long live the 600 point WU.

edit: As I was, a 600 pointer showed up at the last minute and saved the day.
 
I've finnaly got 13/13 here.
At aprox 7.5 PpH thats around 100 Points per Hour from my farm.
I'm HAPPY with that.

Luck.......... :D
u=Tigerbiten.gif
 
u know what i dont understnad? i have two 600 units moving in right now, but my amd 2600+ seems to fold it about 4 min quicker... each step takes 19 minutes, while my amd64 takes 25 min... is that normal by any chance?? shouldnt my amd64 be A LOT faster than my 2600+??

anways, one of them should move in by this evening sometime..
 
I just got my first 600-pointer... I had gotten 300-pointers, but never the 600 before! :eek:

For reference, I have p1140_RIBO_FSpeptide_EXT_nospring, and it's taking about an hour on my AthlonXP 1800 Palomino @ stock 1.54GHz. That clocks it in at around 3.9PpHpGHz. Since I can only have this computer on during waking hours (it's in my room and I'd like to be able to sleep at night), it looks like it'll take around a week to complete. Once it finally gets sent in, it'll be worth it though :D
 
Mauli said:
u know what i dont understnad? i have two 600 units moving in right now, but my amd 2600+ seems to fold it about 4 min quicker... each step takes 19 minutes, while my amd64 takes 25 min... is that normal by any chance?? shouldnt my amd64 be A LOT faster than my 2600+??

anways, one of them should move in by this evening sometime..

Give me the poroject number each machine is working on and copy and paste some of the log file showing frame times from each. I think I may have an answer for you but need to confirm some things. Also, what speeds are your CPUs running at and what models are they really?
 
Many thanks to those that have already posted project numbers, exact frame times and detailed CPU info. Keep them coming.
 
p1135_RIBO_FSpeptide_HEL (GROMACS) (600 points)
Time per frame: 2:20:06 (2.570 pph) Estimated time left: 9:01:09:18

I've got a box working on this, and 2 p1141_RIBO_FSpeptide_HEL's on two others with very similar results (2:17 instead of 2:20 per frame).
 
unhappy_mage said:
p1135_RIBO_FSpeptide_HEL (GROMACS) (600 points)
Time per frame: 2:20:06 (2.570 pph) Estimated time left: 9:01:09:18

I've got a box working on this, and 2 p1141_RIBO_FSpeptide_HEL's on two others with very similar results (2:17 instead of 2:20 per frame).

What CPUs are in those boxen? Thanks in advance!
 
Just got my first biggun.
p1134_RIBO_FSpeptide_EXT
11m27s / frame
01:22:17:00 estimated to complete

Not bad....
 
My 600 PT protein and rig: (this is an update to my previous post about it; I was wrong :( )

Protein: p1134_RIBO_FSpeptide_EXT (1134) 49/1/5 [156]
Time Per Frame: 52:57 (m:s)
CPU: AMD Athlon XP 1700+ Palomino Core OC to 1652 MHz
Start: 3:55 AM 1/3/05
Est Finish: 8:11 PM 1/6/05
Total WU time (Est): 88:15:00
63% Complete (11:35 AM)
 
BakedON said:
Just got my first biggun.
p1134_RIBO_FSpeptide_EXT
11m27s / frame
01:22:17:00 estimated to complete

Not bad....

You have a 5+ GHz CPU?? :confused:
 
Ok. Some more numbers.
Boxen name, Speed, CPU. Protien, Frame time, Points per Hour per Ghz.

Tigger Boxen, 2.4 Ghz Opteron. p1134, 27:55, 5.37 PpHpG. p1135, 28:03, 5.35 PpHpG.

Piglet boxen, 2.0 Ghz Xp. p1134, 47:45, 3.77 PpHpG.

Owl boxen, 2.1 Ghz Mp. p1140, 47:43, 3.59 PpHpG. p1140, 47:43, 3.59 PpHpG.

Roo boxen, 2.1 Ghz Mp. p1134, 48:51, 3.52 PpHpG. p1140, 48:52, 3.51 PpHpG.

Kanga boxen, 2.1 Ghz Mp. p1135, 48:53, 3.51 PpHpG. p1135, 49:05, 3.49 PpHpG.

Rabbit boxen, 2.1 Ghz Mp. p1141, 49:30, 3.46 PpHpG. p1134, 49:23, 3.47 PpHpG.

Eeyore boxen, 1.8 Ghz Mp. p1140, 54:24, 3.68 PpHpG, p1134, 54:33, 3.67 PpHpG.

So 27.2 Ghz running at an adverage speed of 3.85 PpHpG = 104 Point per Hour.

Luck.......... :D
u=Tigerbiten.gif
 
Killer[MoB] said:
You have a 5+ GHz CPU?? :confused:
3.2ghz actually.....
And it seems to have gravitated down to 17m / frame... and will probably settle even lower than that. The first few frames got my hopes up. :)
 
Killer[MoB] said:
Give me the poroject number each machine is working on and copy and paste some of the log file showing frame times from each. I think I may have an answer for you but need to confirm some things. Also, what speeds are your CPUs running at and what models are they really?


amd64 2.25ghz Project 1141

amd 2600+ 2.08 Project 1135

the 2600+ just changed project, right now its rufly 50min compared to 41 min.... amd 2600+ has the 41 minutes...
 
Tigerbiten said:
Ok. Some more numbers.
Boxen name,REMAINDER DELETED FOR SPACE

How did you know I had a column for boxen name on my spread sheet? ;)

Thanks for the info.
 
Mauli said:
amd64 2.25ghz Project 1141

amd 2600+ 2.08 Project 1135

the 2600+ just changed project, right now its rufly 50min compared to 41 min.... amd 2600+ has the 41 minutes...

41 minutes per frame on the 2600+ @ 2.08 sounds right in line with where it should be.

50 minutes is way off for the A64 @ 2.25 though. You should be seeing times of 31:25 to 32:00 or so per frame when the computer is only folding.
 
Back
Top