What's wrong with Folding???

Originally posted by beez7777
how long does it take most people to complete a work unit?

Click to expand...

depends on the WU they gave you. take a look here to find out how long it would take on a 400MHz celeron (benchmarking machine).

we have a lab of 700MHz eMacs here, and they're not the fastest folders. but there's no special instructions like altivec or SSE to help you out. just pure CPU and Mhz.

the key is pateince. anything they give you will take a while.

I've got a question. I started folding last night, and I was up to around 7% this afternoon. I restarted my computer after installing an update to a program I use, and now when I opened up the Folding@home program again, it was back to 0%. It's currently at 0.3%. I thought Folding@home saves your info if you quit or whatever...what gives?

--Fred

hmm...what kinda protein were you folding? maybe you finished it, otherwise i don't know i personally have never had that happen, it always resumes for me.

Originally posted by howard
hmm...what kinda protein were you folding? maybe you finished it, otherwise i don't know i personally have never had that happen, it always resumes for me.

Click to expand...

Hell if I know...what do you mean "what kind of protein" ? lol all I know is that I was folding and then i restarted and then it started over at 0%....oh well.

--Fred

On a side note, how much faster is the GUI version versus the CLI version? Is it the same for PCs?

Originally posted by topicolo
On a side note, how much faster is the GUI version versus the CLI version? Is it the same for PCs?

Click to expand...

you can judge through top in the command line by opening up the app and running it. look at how much %CPU the folding app takes up.

folding has two processes associated with it:
o Fahcore_65 - does all the crunching
o the controlling app
-- for console OSX-3.24
-- for GUI Folding@home

since fahcore does all the crunching, you can ignore this as it is the same for both gui and CLI. the driving app is the one you want to look at.

for CLI i noticed no processor usage ever on the controlling program.

for GUI i noticed the same results if you never display the protein. if the protein was displayed, like 10-20% depending on display options. even if you hide the app after displaying the protein it seems to take up 10%.

its not a whole lot since it's periodic, but CLI offers flexibility (background running, DP, etc.) and less processor usage. for no-hassle use GUI.

these are mac observations only. PCs i don't care as much about.

Ok, I'm in - username Sully. I am crunching my first protein, P632_TZ3_NAT (yummy).

Do I have to maintain my network connection while doing so?

Cheers!

Originally posted by MacPorter
Ok, I'm in - username Sully. I am crunching my first protein, P632_TZ3_NAT (yummy).

Do I have to maintain my network connection while doing so?

Cheers!

Click to expand...

no, only when sending and recieving proteins. so in ur case, since u already have the protein, u only need the connection when it's finished.

thanks 4 contributing.

well, team MacRumors just got another 2.4Ghz of PC processing power. (Hey, they're good for something)