Replies

You'd think so, but I had a project 2107 (404 points) that took only seemed to take a little longer than a project 2106 (202 points). Wish I had a record of the exact times.

You can go looking back through your log, and see how much time each of them took, IIRC.

I just learned something, some of you may know, but I just found out and figured it's knowledge gained the hard way and worth posting. I am sure this applies to the console version, which I use, but it likely applies to the GUI version, as well.

I recently had a power outage and had to restart. On reboot, I got the dread "checksums don't match" error and the project restarted from the beginning (which wasn't too bad as it was in the early stages).

But, after the reboot, I noticed progress was painfully slow - it was taking an hour to complete 1%. On checking the logs, I noticed the line "Extra SSE Boost OK" I usually see in the log was missing.

I rebooted and, this time, got the SSE boost and the time to complete 1% dropped to 25 min. The SSE boost more than doubled the folding speed for this problem.

Reading a few logs I learned that after a bad checksum, the core assumes the problem may have been with the SSE boost and disables it. To get it back, you have to reboot again (as I did) or use the -forceasm flag after the power loss to get the current problem back up to full speed.

I assume that if you let a problem run to completion without the SSE boost, the next problem would have it applied automatically, but I'm not sure on this.

Bottom line, if a problem is running slowly you might want to look for the "Extra SSE Boost OK" in the log, especially after a power loss or blue screen reboot. If you normally see this in the log, a reboot or the -forceasm flag may give a big help.

All three of my CPUs are now working on 2107, my two slow ones are choking. They are going to take 10 to 15 days.