F@H ?

[MichaelD]

WU=Work Units. That I know.

My question: When I DL work to do, and it shows "Working on 5/500" does that mean when it's done, I'll have accomplished 500 Work Units?

What is considered a "good amount of WUs for one day (24 hours)?"

Thanks. This is fun. 🙂

Maybe it's just that I'm new...but my 2,000MHz rig doesn't seem appreciably faster than the 731MHz rig. Maybe b/c I'm staring at the progess meter? 😉

 

[BlackMountainCow]

This "5/500" is just ONE WU you got there. It consists of like 500 segments (or whatever that is called). F@H can only store one WU at a time (with some special exceptions the F@F pros should explain here). So basically you download one, you crunch it, you upload it, you get a new one. That's the deal with F@H.

About you speed issue / problem: AFAIK there are different WUs in F@H with a different ammount of "segments", like 500, 1000 or 2000. So of course a 500er needs less time than a 1000er and so on ... maybe that's why you get that feeling!

🙂

 

[GLeeM]

Hello there MichaelD 🙂

Yeah this is fun!

WU: what BMC said, they can be different lengths and times for each protein. In F @ H we go by points for our stats more than WUs. I think what you need is a monitor program that will show the protein name, points its worth, steps or frames to completion, time per step, time till done, and especially estimated points per day. They are small simple programs.

If you look Here you will find links to FAH LogStats (simpler and not as much info) and to Electron Microscope (more info, but doesn't display well on my laptop or nonstandard display resolution desktop) If your rigs are networked together you can monitor both from one rig 🙂

Your 2 ghz rig should be about three times faster. It's probably different WUs that have you thinking that it's not faster. With one of the above programs you will see the difference. (If it isn't alot faster, we should look for the cause, it could be a number of things. We want you getting full production (value for electricity) from any rig you fold on.)

Thanks! Your enthusiasm is contagious to everyone in DC!

 

[MichaelD]

Cool. I'll check those proggys out. 🙂

BTW, when you select "Pause when done" It stops after completing whatever WU it's working on, right? I need to swap out a fan and don't want to lose my progress.

I saw that slider-control Checkpointing thing...not sure about how well that works though.

 

[Hyperfocal]

This page gives a list of all the current F@H projects and their point values.

F@H work units vary greatly in complexity -- some will take as little as 7 hours on a fast rig while others may take nearly a week on a rig like your 731 mhz.

The only real way to compare performance is to look at your points per day.

 

[MichaelD]

Hey, my current project is worth 46 points! Preferred number of days is 6, but I'll have it done in about *thinking* 12 hours!! Not bad. I'm at 88% done. I started it about 0030 hours today, at it's almost 1100 hours now. Should finish it out.

BTW, scrapped the P3 rig and have my old NF2 rig running. 2.00GHz CPU luvin! 🙂

 

[GLeeM]

Pause when done does like you guessed.

If you have to shut the computer down you can quit the program and it should continue from where it left off (the last checkpoint) when you restart it. (Sometimes after a crash or if you lose power or just turn off computer without quitting the program, it will not know where it was, because of a corrupted file, and upon restarting it will start from the beginning again. 🙁)

 

[MichaelD]

Thanks Gleem. After it pauses it WILL report my work back to Mother, right?

 

[GLeeM]

I think it will send the results and then pause before getting a new WU. It's been awhile since I tried it to see what it would do 🙂