• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

post your frame time here !!!

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

overdoze

Member
Joined
Jan 12, 2001
Location
Texas
I'd like to get some frametime for comparison between different processors and speed. I know it changes between different frames. But I just want to collect some estimate data for a possible farm with points per dollars as the main focus. So post your frame time and don't forget to post the protein name and your system spec, OS ...
Thank you all for helping out.

Here is my frame time
[17:53:05] Protein: p352_nat_305_99

[21:45:14] Completed 2100000 out of 2500000 steps (84%)
[21:55:48] Writing local files
[21:55:48] Completed 2125000 out of 2500000 steps (85%)
[22:05:51] Writing local files
[22:05:51] Completed 2150000 out of 2500000 steps (86%)

System spec:
duron at 2GHz
FSB=166
OS: Linux Overclockix
 
When I get home I'll post some times for my 1 Gig w/o SSE, 1.5 Gig w/ SSE and 2.3 Gig w/ SSE


EDIT:
OS - Win98SE all running Beta 3.25 Main rig using graphical and the 2 layers are using the console client.

2.33 Ghz Tbred 1700 (186 x 12.5)
256 MB PC2100 DDR (140 FSB)
SSE
Protein Time/Frame
p324_nat_337 00:07:44
p326_nat_369 00:07:32
p323_nat_321 00:07:56
p334_unf_305 00:08:42
p386_gnra_pf1_cut 00:02:24
p807_p53dimer807 00:09:10
p805_p53dimer805 00:09:32
p337_unf_353 00:08:18
p320_nat_273 00:08:06
p326_nat_369 00:07:34
p334_unf_305 00:07:54
p337_unf_353 00:07:44
p323_nat_321 00:07:56
p332_unf_273 00:08:08
p326_nat_369 00:07:36
p323_nat_321 00:07:54
p323_nat_321 00:07:56
p382_gnra_pf1_75i 00:08:36
p322_nat_305 00:08:00
p332_unf_273 00:08:56
p364_tip5p_pf1_Mg 00:05:00
p384_gnra_pf1_150i 00:08:20
p373_gnra_pf2_noi 00:09:38
p378_gnra_pf1_38i 00:10:06
p368_tip5p_pf1_Na 00:04:50
p377_gnra_pf2_22i 00:09:06
p322_nat_305 00:08:00
p322_nat_305 00:07:58
p384_gnra_pf1_150i 00:08:20
p252_UUUA Na+ stacked 00:04:00
p384_gnra_pf1_150i 00:08:12
p344_gnra_unf_1 00:10:12
p377_gnra_pf2_22i 00:09:00
p344_gnra_unf_1 00:09:04
p344_gnra_unf_1 00:09:58
p352_nat_305_99 00:07:58
p387_gnra_pf2_cut 00:02:26
p253_AAAA Na+ stacked 00:04:14
p380_gnra_pf1_56i 00:08:54
p381_gnra_pf2_56i 00:08:44
p344_gnra_unf_1 00:08:58
p377_gnra_pf2_22i 00:09:00
p344_gnra_unf_1 00:09:06
p385_gnra_pf2_150i 00:08:10
p376_gnra_pf1_22i 00:09:34
p378_gnra_pf1_38i 00:09:00
p344_gnra_unf_1 00:08:52
p362_tip4p_pf1_Mg 00:08:28
p344_gnra_unf_1 00:09:26
p341_gnra_den 00:08:44
p382_gnra_pf1_75i 00:08:34
p335_unf_321 00:08:36
p381_gnra_pf2_56i 00:08:42
p344_gnra_unf_1 00:09:00
p368_tip5p_pf1_Na 00:04:44
p334_unf_305 00:07:52
p341_gnra_den 00:09:02
p322_nat_305 00:07:54
p338_unf_369 00:07:30
p333_unf_289 00:07:56
p340_gnra_nat 00:09:10
p341_gnra_den 00:09:10
p364_tip5p_pf1_Mg 00:04:46


1 Ghz Athlon (100 x 10)
256 MB PC100 SDRAM
3DNOW!
p322_nat_305 00:45:44
p322_nat_305 00:45:44
p804_p53dimer804 00:29:06
p324_nat_337 00:07:44
p368_tip5p_pf1_Na 00:13:28
p368_tip5p_pf1_Na 00:13:26
p341_gnra_den 00:27:04
p322_nat_305 00:45:30
p344_gnra_unf_1 00:26:38
p372_gnra_pf1_noi 00:26:40
p344_gnra_unf_1 00:26:32
p253_AAAA Na+ stacked 00:12:00
p323_nat_321 00:45:16
p364_tip5p_pf1_Mg 00:13:16
p386_gnra_pf1_cut 00:07:14
p380_gnra_pf1_56i 00:26:16
p387_gnra_pf2_cut 00:07:12
p379_gnra_pf2_38i 00:26:44
p387_gnra_pf2_cut 00:07:04
p344_gnra_unf_1 00:26:54
p341_gnra_den 00:27:00
p368_tip5p_pf1_Na 00:13:18



1.53 Ghz Pally 1800 (133 x 11.5)
256 MB DDR PC2100
SSE
p340_gnra_nat 00:13:24
p340_gnra_nat 00:13:14
p369_tip5p_pf2_Na 00:06:52
p1001_ppg10_350 00:12:50

800 Mhz Slot A Athlon (100 x 8)
384 MB PC100 SDRAM
3DNOW!
p323_nat_321 00:56:00
p333_unf_289 00:58:02
p340_gnra_nat 00:35:08
p344_gnra_unf_1 00:34:58
p383_gnra_pf2_75i 00:33:44
p373_gnra_pf2_noi 00:35:12
p378_gnra_pf1_38i 00:34:06
p387_gnra_pf2_cut 00:09:08
p344_gnra_unf_1 00:34:46
p385_gnra_pf2_150i 00:30:36
p387_gnra_pf2_cut 00:09:00
p379_gnra_pf2_38i 00:33:48
p369_tip5p_pf2_Na 00:16:50
p344_gnra_unf_1 00:34:28
p344_gnra_unf_1 00:33:56
 
Last edited:
Thanks Fast420A.

That is impressive. Thank you for your posting results. I will do an analysis later on when i have a little more data.
 
Is that our test machine, overdoze?

I suppose you are really more interested in socket A CPU's than anything else, and likely differences in budget CPU's with SSE like morgan durons, XP palominos, XP Tbreds, Appalbred Durons, and XP Thornton's. Espeically CPU's in the sub-$60 range?
 
FYI the F@H client has a benchmark built in to it that is probably an easier method of comparison that comparing tons of different work units to each other :D


a sampling of some of my recent work units. This is on rig 1 in my sig:

[08:30:08] Protein: p368_tip5p_pf1_Na
[08:30:08]
[08:30:08] Writing local files
[08:30:44] Extra SSE boost OK.
[08:30:44] Writing local files
[08:30:44] Completed 0 out of 100000 steps (0)
[08:34:25] Writing local files
[08:34:25] Completed 1000 out of 100000 steps (1)
[08:38:05] Writing local files
[08:38:05] Completed 2000 out of 100000 steps (2)
[08:41:45] Writing local files
[08:41:45] Completed 3000 out of 100000 steps (3)
[08:45:24] Writing local files
[08:45:24] Completed 4000 out of 100000 steps (4)
[08:49:04] Writing local files


[18:46:27] Protein: p684_TZ2_EXT_EXP
[18:46:27]
[18:46:27] Writing local files
[18:46:27] Extra SSE boost OK.
[18:46:29] Writing local files
[18:46:29] Completed 0 out of 2500000 steps (0)
[18:54:44] Writing local files
[18:54:44] Completed 25000 out of 2500000 steps (1)
[19:02:58] Writing local files
[19:02:58] Completed 50000 out of 2500000 steps (2)
[19:11:12] Writing local files
[19:11:12] Completed 75000 out of 2500000 steps (3)
[19:19:28] Writing local files
[19:19:28] Completed 100000 out of 2500000 steps (4)


[14:36:13] Protein: p341_gnra_den
[14:36:13]
[14:36:13] Writing local files
[14:36:49] Extra SSE boost OK.
[14:36:49] Writing local files
[14:36:49] Completed 0 out of 500000 steps (0)
[14:43:55] Writing local files
[14:43:55] Completed 5000 out of 500000 steps (1)
[14:50:58] Writing local files
[14:50:58] Completed 10000 out of 500000 steps (2)
[14:58:02] Writing local files
[14:58:02] Completed 15000 out of 500000 steps (3)
 
that was working on
Protein: p678_L939_K12M_355K

little chunk from that one:
[22:00:30] Finished a frame (266)
[22:07:12] Finished a frame (267)
[22:13:49] Finished a frame (268)
[22:20:25] Finished a frame (269)
[22:27:01] Finished a frame (270)
[22:33:39] Finished a frame (271)
[22:40:17] Finished a frame (272)
[22:46:52] Finished a frame (273)
[22:53:24] Finished a frame (274)
[23:00:02] Finished a frame (275)
[23:06:43] Finished a frame (276)
[23:13:22] Finished a frame (277)
[23:20:01] Finished a frame (278)

another:
Protein: p638_L939_K12M_ext

and the chunks:
[07:26:07] Finished a frame (280)
[07:32:29] Finished a frame (281)
[07:38:51] Finished a frame (282)
[07:45:17] Finished a frame (283)
[07:51:59] Finished a frame (284)
[07:58:21] Finished a frame (285)
[08:04:49] Finished a frame (286)
[08:11:12] Finished a frame (287)
[08:17:33] Finished a frame (288)
[08:23:52] Finished a frame (289)
[08:30:15] Finished a frame (290)
[08:36:40] Finished a frame (291)
[08:43:05] Finished a frame (292)
[08:49:23] Finished a frame (293)

i'm using core v2.5
[19:51:03] Core required: FahCore_65.exe
[19:51:03] Core found.
[19:51:03] Working on Unit 01 [October 6 19:51:03]
[19:51:03] + Working ...
[19:51:03] Folding@Home Client Core Version 2.50 (August 19, 2002)

My rig isn't overclocked at all. yet. :D it will happen. maybe this weekend, when i have time....

anyone...are these pretty normal frame times for the linux client with my hardware? i'm getting 400 frame packets every time.

Hope that helps. DeathKnight, can you use the F@H benchmark in linux? I know that it benchmarks every time you run the program, but can i access the results? i couldn't find a command argument on folding.stanford.edu that did such a thing.
 
I don't remember where it puts the benchmark result for the linux client, but I'll look into it later tonight....

I've been getting teh tinker WU's on my linux boxes too. Stanford has trouble now and then with linux + gromacs. Many of the projects are buggy with thier current linux gromacs core, so they avoid sending those projects to linux folders. Right now they must have run out or be low on the gromacs projects that are good in Linux. I'm sure they'll get it worked out soon.

You can always run the windows client in wine if you prefer gromacs so much more than tinker. I might switch my overclockix boxes over to wine later tonight to avoid getting the tinkers.

I'll make anohter post about it where I can help ppl running linux make the switch....
 
i don't know. i suppose i could just stay with the tinker core projects. everything needs to be done by someone. But i'm wondering if it would be better for me to run gromacs in wine since then i could run the sse boost, making efficient use of the resources that i have. what do you think?
 
Points are about 2x or 3x running gromacs with SSE enabled vs running tinker.
 
The way I look at it is this, If you have the ability to run SSE optimized folding, do it, there's other computers out there folding that can't use SSE and are better suited for tinkers. 2 of the boxes I have running for me are P1's running tinkers only because the gromacs ran WAY too slow on them. My 1 Gig Athlon folds gromacs with only 3DNow faster than it folds Tinkers so I use the flags for gromacs on that.
 
all right. i guess i'll run wine and get that sse boost. i wish stanford would hurry up and get a sse capable native linux client. 3.25B will be, right? however, no 3.25B available....
 
[18:43:07] Protein: p686_L939_K12M_ext_novisc
[18:43:07] - Run: 8 (Clone 49, Gen 1)
[18:43:07] - Frames Completed: 0, Remaining: 400
[18:43:07] - Dynamic steps required: 5000000

Example of frame time:

[02:10:31] Finished a frame (101)
[02:15:02] Finished a frame (102)
[02:19:35] Finished a frame (103)
[02:24:08] Finished a frame (104)
[02:28:43] Finished a frame (105)

AMD XP 2500+ @ 2.08ghz
Windows 2000, no nonsense text client (FAH3Console.exe)
 
[06:19:20] Protein: p801_p53dimer801
[06:19:20]
[06:19:20] Writing local files
[06:19:20] Completed 50000 out of 500000 steps (10)
[06:19:21] Extra SSE boost OK.
[06:23:55] Writing local files
[06:23:55] Completed 55000 out of 500000 steps (11)
[06:28:28] Writing local files
[06:28:28] Completed 60000 out of 500000 steps (12)
[06:33:01] Writing local files
[06:33:01] Completed 65000 out of 500000 steps (13)
[06:37:34] Writing local files
[06:37:34] Completed 70000 out of 500000 steps (14)
[06:42:12] Writing local files
[06:42:12] Completed 75000 out of 500000 steps (15)
[06:46:51] Writing local files
[06:46:51] Completed 80000 out of 500000 steps (16)

Wedo's One-Click using 3.25 Beta client on WindowsXP
 
[20:36:23] Protein: p834_p53dimer834
[20:36:25] Writing local files
[20:36:25] Completed 0 out of 500000 steps (0)
[20:41:52] Writing local files
[20:41:52] Completed 5000 out of 500000 steps (1)
[20:47:19] Writing local files
[20:47:19] Completed 10000 out of 500000 steps (2)
[20:52:55] Writing local files
[20:52:55] Completed 15000 out of 500000 steps (3)
[20:58:54] Writing local files
[20:58:54] Completed 20000 out of 500000 steps (4)

How is that?
 
baru said:
all right. i guess i'll run wine and get that sse boost. i wish stanford would hurry up and get a sse capable native linux client. 3.25B will be, right? however, no 3.25B available.... [/QUOTE

No, 3.24B and 3.25A (beta) are both SSE capable. It's just that all 3.24 clients sometimes disable SSE for no apparent reason, while 3.25 (beta) clients will only do so if there is a stability problem.

There are two ways around this if you have a new distro like mandrake 9.1 or redhat 9, which must use the 3.24B client for compatibilty reasons.

1) Set a crontab entry to stop your client once/day, and also to restart it one minute later. This refreshes the client and turns SSE back on if it was off. You lose a fwe minutes on because you start over a frame that was in progress, but if it re-enables SSE for you, its worth it.

crontab -e

Put the following in your crontab. cron uses the vi text ediitor by default so press "i" to insert text and "escape key :wq" to save when done. Do this as a normal user, not as root. This example stops the client at 4AM every morning and restarts it at 4:01AM.

00 04 * * * killall -15 FAH3*.exe
01 04 * * * /path/to/your/folding/FAH3Console-whatever.exe -advmethods -forceasm > /path/to/your/folding/FAHlog.txt &


2) Fold using wine and the windows 3.25 beta client
 
These times are from my dual 2100+ running Gentoo, using the B client.

[21:12:20] (Starting from checkpoint)
[21:12:20] Protein: p353_unf_305_99
[21:12:20]
[21:12:20] Writing local files
[21:12:21] Completed 1025000 out of 2500000 steps (41%)
[21:12:21] Extra SSE boost OK.
[21:22:53] Writing local files
[21:22:53] Completed 1050000 out of 2500000 steps (42%)
[21:33:38] Writing local files
[21:33:38] Completed 1075000 out of 2500000 steps (43%)
[21:44:29] Writing local files
[21:44:29] Completed 1100000 out of 2500000 steps (44%)
[21:55:15] Writing local files
[21:55:15] Completed 1125000 out of 2500000 steps (45%)

[21:12:21] (Starting from checkpoint)
[21:12:21] Protein: p350_nat_305_94
[21:12:21]
[21:12:21] Writing local files
[21:12:21] Completed 975000 out of 2500000 steps (39%)
[21:12:21] Extra SSE boost OK.
[21:22:51] Writing local files
[21:22:51] Completed 1000000 out of 2500000 steps (40%)
[21:33:35] Writing local files
[21:33:35] Completed 1025000 out of 2500000 steps (41%)
[21:44:23] Writing local files
[21:44:23] Completed 1050000 out of 2500000 steps (42%)
[21:55:05] Writing local files
[21:55:05] Completed 1075000 out of 2500000 steps (43%)

Axle
 
Back