[cdhostage]

I've got top running at -u -s10, so it updates every ten seconds and arranges in descending order of CPU use. Since I started Folding@Home, I've seen that the process with the most CPU use is Core_65.e
There's another process called Folding@ho that only gets one or two percent CPU use.

My crunching is slow - in a week on my iMac 500, I've gotten 3 points.

What's oging on here?

[Shaktai]

Originally posted by cdhostage:
<STRONG>I've got top running at -u -s10, so it updates every ten seconds and arranges in descending order of CPU use. Since I started Folding@Home, I've seen that the process with the most CPU use is Core_65.e
There's another process called Folding@ho that only gets one or two percent CPU use.

My crunching is slow - in a week on my iMac 500, I've gotten 3 points.

What's oging on here?</STRONG>

Core_65.e is the actual F@H crunch core. This is normal this is where the bulk of calculations take place.

However, your iMac 500 does seem a bit slow. My iBook 600 will do about 1.5 to 1.6 points per day, or 11+ per week, if running uninterrupted 24/7. Are there any other major processes running? Are you using the CLI or GUI version? If the GUI, do you run it hidden? Do you run it 24/7 or just part time? Also, how much RAM do you have? Do you have your screensaver turned off?

Also, what type of proteins have you been getting?

Core_65e is the scientific core. That is why F@H will be able to update the core so it is faster (very soon) without the users having to update their clients. You download the core when you download the work unit.

[ 05-05-2002: Message edited by: Shaktai ]

[krove]

the F@H process actually downloads what they call the "Core" and that is what is running the folding code (Core_65.exe).

Because they are only handing out units that are worth 0.5 points, its much harder to make headway. Using multiple machines is really the only way to garner more points (if that interests you).

Kyle

[Grozni Majmun]

You run the GUI version, right? After you start it up, there is no window, but if you choose "show protein" from the menu, it displays the cool looking protein and spins it around. That really slows down the crunching. Using apple-H to hide the application does not help. If you instead just leave it the way it is when it starts, without a window, it will be much faster. 3 points on an iMac in a week is not a lot. Did you run it 24/7?

[cdhostage]

Hmm. So is there no way tto hceck the progress on the thing wihtout having it Show Protein? And if I show the window and then hide it, it stilel calculates the image... stink.

I'll be switching over to the CLI soon anyway. The picture isn't very pretty like SETI was.

I run a Graphite iMac 500 with 640 megs of RAM. No screensaver, monitor goes blank after 5 minutes. No other major processes.

[reader50]

You can check the progress of the GUI version by opening the work unit log file.

Go to the bottom of the CLI install page, where you will find the instructions. I didn't throw them into the GUI install instructions because it did not seem needed there.

[cdhostage]

Well , now that I know not to open the GUI app to look at progress, it's running somewhat faster.

One point per day.

[Shaktai]

Originally posted by cdhostage:
<STRONG>Hmm. So is there no way tto hceck the progress on the thing wihtout having it Show Protein? And if I show the window and then hide it, it stilel calculates the image... stink.

I'll be switching over to the CLI soon anyway. The picture isn't very pretty like SETI was.

I run a Graphite iMac 500 with 640 megs of RAM. No screensaver, monitor goes blank after 5 minutes. No other major processes.</STRONG>

Hmm! I have never had that problem. I have always been able to display and rehide the protein without any significant slowdown by rehiding. Doesn't matter whether I run CLI or the GUI hidden ( even re-hidden) my times are almost always the same give or take 10 minutes. The important thing is "do not minimize" to the dock. This will really slow it down. My iBook will 600 will consistently do a 1/2 point GNRA hairpin in 7:20 to 7:40 hours. The difference is primarily a factor of how much I use it for other things, like right now as I write this. The longest time was 8 hours, and that was because I forgot to shut down Internet Explorer when I wasn't using it.