• 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 Benchmarks - Share Yours!

Syntax

Senior member
Here are some benchmarks for the Folding@Home project. Lets see how our benchmarks compare, so post em!

BTW we are in heavy competition now but have moved up to 48th!

I picked out some of the protiens that I have crunched multiple times.

Computer ------- Protien ----------- Time Per Frame ------ Total WU Time (Rounded)
P4@1.9 ............ GNRA hairpin ............ 7:32 ..................... 13 Hours 30 Min
P3@450 ........... GNRA hairpin ............ 19:48 .................... 33 Hours
P3@500 ........... GNRA hairpin ............ 18:48 .................... 30 Hours 30 Min
P2@266 ........... GNRA hairpin ............ 34:18 .....................57 Hours

P4@1.9 ........... bba5_build_ext .......... 2:18 ..................... 3 Hours 45 Min
P3@500 ........... bba5_build_ext ........... 7:40 .....................13 Hours 30 Min

P4@1.9 ........... NativeBBA5 (ORC##) ..... 2:20 ..................... 3 Hours 50 Min (approx for OCR ##'s)
P4@1.9 ........... Ab28-43V ................. 4:20 ....................... 7 Hours 15 Min


I use a program called KDFold to monitor the progress of several computers from one console. It maintains statistics on individual protiens.

Note the Time Per Frame is exact time and the Total WU time is rounded.
 
Thanks, Syntax. I just started running Kfold last night, as soon as I build up a couple of different wu's I'll post them for you 🙂
 
CPU....................Protein..............................Time/Frame...........Total WU

PIII Xeon 933.....proteinAnat F:78.................00:23:23..............38:58:20
PIII Xeon 933.....bba5_build_ext F:90..........00:04:10..............06:46:40
PIII Xeon 933.....proteinA................................00:22:32..............37:33:20
PIII Xeon 933.....1APS.....................................00:17:58..............29:56:40
PIII Xeon 933.....proteinAg29aNat................00:22:24...............37:20:00
PIII Xeon 933.....proteinAg29aNat................00:22:26...............37:23:20
PIII Xeon 933.....NativeBBA5 ORC-(5311)..00:04:00...............06:40:00
PIII Xeon 933.....NativeBBA5 ORC-(5311)..00:04:22...............07:16:40

Celeron 1.2.........1SHF....................................00:05:13...............08:41:40
Celeron 1.2.........I6C........................................00:02:38................04:23:20
Celeron 1.2.........GNRA hairpin.....................00:07:00................11:40:00
Celeron 1.2.........proteinAg29aNat................00:16:30...............27:30:00
Celeron 1.2.........1APS....................................00:13:16................22:06:40

The time difference for the same proteins on the same proc. is due to the machines being used for various tasks while processing.

Damn that's a pain in the rear to get those to line up right!
 
Back
Top