Abaddon
Deity


Don't worry - I found a solution ... delete the 'work' sub-directory. The prog then says "cannot find work directory, restarting new job" (or similar).I'm moving to a console client and will also be starting my second core folding. I've copied the prog file directory but I think I need to flush the partially completed job so that both cores don't work on the same one. How do I do that?
Mines screwed up after completeing a work unit again.. ill have to completely remove it from my system and reinstall before it will work again.. i wonder why it does this?!?!
This was weird, my current WU was averaging about 1:15 per frame, yesterday I restarted my computer and afterwards it was working at 3:09 per frame.
Tonight, after the WU should have finished based on the original time estimate, I decided to try restarting my computer again and it's now back to 1:15 per frame.
When it was working at 3:09 per frame there was nothing else eating up my CPU usage that I could see. I don't understand why restarting my computer caused such a drastic change in my folding speed.
Longer than that. It's been about 10 months since I last ran F@H, and I'm still in the top 10.For what it's worth - neither can I, now.Though it looks like I'll retain the highest "total points" for at least another six months.
![]()
Longer than that. It's been about 10 months since I last ran F@H, and I'm still in the top 10.![]()
I get 34s per frame, I wonder who gets the fastest speed?
A frame isn't a constant amount of work, in most cases it's simply 100th of the total work package, though some are 400 frame units. So measuring the time per frame is not very useful as a comparison unless all the work units happen to be the same size.
My four-core system runs 100-frame SMP work units at about 12 mins per frame, taking 20 hours to complete one work unit. They are worth 1440 points per unit. That's about 70 points per hour.
A frame isn't a constant amount of work, in most cases it's simply 100th of the total work package, though some are 400 frame units. So measuring the time per frame is not very useful as a comparison unless all the work units happen to be the same size.
My four-core system runs 100-frame SMP work units at about 12 mins per frame, taking 20 hours to complete one work unit. They are worth 1440 points per unit. That's about 70 points per hour.
Sidhe said:And I also have a feeling you will not remain in 5th for ever
I guess 4 core systems get different WU's than I do. I get a bunch of different sized ones, but bigger ones have smaller times. The one I had yesterday was 2000 frames at 1:15, the one I'm working on now is 5000 @ 29 seconds each.
I've also had WU's that were as high as 20,000 and 50,000 frames, and as low as 200. But each seems to take me 1.5 to 4 days to complete.
I've seen people talking about very large frame counts before, and I still don't 'get it'. This page lists the projects and the "Frames" column contains entries of 2 (a strange exception, I guess), 400 (a few Tinker projects), and mostly of 100. Where are you getting 2,000, 20,000 and 50,000 frame projects from?
I have a feeling you may have the fastest processor
And I also have a feeling you will not remain in 5th for ever.![]()
That project is listed as a 100 frame project in the list I linked earlier, and I can see nothing in that listing that correlates with 20,000. Maybe the "frames" given in your graphical client are using some older definition of the project size.AlanH, it says 'frames' in the FAH client.. for instance, right now I'm running a typical 20,000 frame unit (p2124_lambda_5way_mei.. Gromacs core) and I'm at frame 7923 with 19 seconds/frame..
Ah, yes. But Aesop had a fable about a tortoise and a hare. The SMP client is beta software, meaning it breaks every so often. My system racks up big numbers when it's working, but then it'll have a major hiccough once in a while and throw work units away like a drunken sailor for a couple of days. That restores my average to a more modest level from time to time.
Right now Sahkuhnder sustains a faster and more consistent rate of progress than I do, and seems to be disappearing into the sunset. The stats indicate that I'll move up to 3rd place in the next couple of months, but after that, IglooDude's massive accumulated score plus Sahkuhnder's impressive current work rate will keep me there indefinitely.
I don't run a graphical client on my multicore machine, so the only display I have is the log file. I do have another, older, single core Mac that runs a conventional graphical client. It's currently folding p3038_supervillin-03, and all I see in the Mac graphical client is a percentage progress number and a progress thermometer. The log file, again, just lists "steps" at 1% intervals. Each 1% is 50,000 steps for the current unit, and it's doing 1% every 80 minutes or so.