Waiddaminnit?sr4470 said:
Huh? How junky are the aforementioned rigs?sr4470 said:I bring an X2 and some junky rigs
Folding@Home News - Attention Single-Machine Crunchers
- Thread starter rich99million
- Start date
hehe you have to get up pretty early to get one over on Billy 
well i'm not totally sure about it - Concorde has a similar thing with his dual cpu mac dropping the very occasional WU when it's actually on (not much these days
)
guess I'll have to see how it goes, if it doesn't really make any difference to output then people may not mind
edit: maybe I could colour code those with X2's and several really slow machines
there might be more hiding out there
well i'm not totally sure about it - Concorde has a similar thing with his dual cpu mac dropping the very occasional WU when it's actually on (not much these days
)guess I'll have to see how it goes, if it doesn't really make any difference to output then people may not mind
edit: maybe I could colour code those with X2's and several really slow machines
there might be more hiding out there
Last edited:
please say it's a Slot jobbie and not the X2sr4470 said:Argh I think I just burned a CPU
edit - i thought those old things were near indestructable
Associate
I'm single.
(both as a cruncher and in real life
)
(both as a cruncher and in real life
)
Ok I've added both sr4470 and nellystew, sr4470 if you're having to use only one core of the X2 at the moment then I don't suppose anyone will really mind the junky machines - if output gets a boost I think it'd only be fair to put you with the main group of stats really
the single-cruncher stats are aimed at those who are stuck down at the bottom of the list or get left out by the 1000-point cut off, we'll see how it goes this week and work on it from there
are you new and not completed a WU yet?
I will gladly add you ready for the news on friday if that's the case
the single-cruncher stats are aimed at those who are stuck down at the bottom of the list or get left out by the 1000-point cut off, we'll see how it goes this week and work on it from there
welcome - only problem is I can't find youIsotope said:Im in, Isotope2006 is the name!
are you new and not completed a WU yet?
I will gladly add you ready for the news on friday if that's the case
rich99million said:Ok I've added both sr4470 and nellystew, sr4470 if you're having to use only one core of the X2 at the moment then I don't suppose anyone will really mind the junky machines - if output gets a boost I think it'd only be fair to put you with the main group of stats really
the single-cruncher stats are aimed at those who are stuck down at the bottom of the list or get left out by the 1000-point cut off, we'll see how it goes this week and work on it from there
Fair enough, I see what you mean. As for the slot CPUs, the only one with any real horsepower is a P3 500(100fsb) with 512k external cache, on a 440BX chipset board.
Since you can't be found, you must be a new user. Welcome to the team, Isotope. May your stay be long and foldy.
Isotope said:Im having a bit of trouble, it seems to be taking really really really long to do anything, originally it was fine and it was going to take 14hrs to do the first WU but I had to quit and now it says its going to take 216 days?!
What CPU?
have a look at your log file and see if you can see
[17:25:05] Project: 2500 (Run 364, Clone 10, Gen 0)
[17:25:05]
[17:25:05] Assembly optimizations on if available.
[17:25:05] Entering M.D.
[17:25:11] Protein: p2500_BBA5_pfold
[17:25:11]
[17:25:11] Writing local files
[17:25:11] GB activated
[17:25:11] Extra SSE boost OK.
[17:25:12] Writing local files
my guess is that the SSE hasn't kicked in - either that or you're running the Graphical version and it's just doing a really poor job of providing an estimate and will come down once it's been running again for a while
if it's the SSE stop the client and then restart it and it should come back on - you can add the -forceasm switch (see the sticky) to stop it getting disabled by mistake
[17:25:05] Project: 2500 (Run 364, Clone 10, Gen 0)
[17:25:05]
[17:25:05] Assembly optimizations on if available.
[17:25:05] Entering M.D.
[17:25:11] Protein: p2500_BBA5_pfold
[17:25:11]
[17:25:11] Writing local files
[17:25:11] GB activated
[17:25:11] Extra SSE boost OK.
[17:25:12] Writing local files
my guess is that the SSE hasn't kicked in - either that or you're running the Graphical version and it's just doing a really poor job of providing an estimate and will come down once it's been running again for a while
if it's the SSE stop the client and then restart it and it should come back on - you can add the -forceasm switch (see the sticky) to stop it getting disabled by mistake
Well I have switched over to the console version and it says all the things that Rich has pointed out, then gets to the 0 of 125000000 and I think it just stops there.
Its says the SSE has kicked in as well. I tried running Fahmon and it sees the WU but it doesnt have an ETA for it and nothing seems to happen.
Also my CPU (an AMD64 3200+ btw) is running at 100% but nothing happens.
Its says the SSE has kicked in as well. I tried running Fahmon and it sees the WU but it doesnt have an ETA for it and nothing seems to happen.
Also my CPU (an AMD64 3200+ btw) is running at 100% but nothing happens.
Do what Rich said. Failing that you can always start a thread and post your fahlog.txt for our wandering eyes to examine.
EDIT: Hmm, it it's at 100% but it's not moving there might be somehting more severely wrong. Check your unitinfo.txt and see when it was downloaded. How long has it been crunching? Have you tried restarting the machine?
EDIT: Hmm, it it's at 100% but it's not moving there might be somehting more severely wrong. Check your unitinfo.txt and see when it was downloaded. How long has it been crunching? Have you tried restarting the machine?
Last edited:
You've probably done this, but check it's actually Folding that's using 100% of your CPU and not some other rogue process!
Failing that, it might just be an issue with the WU. You might be able to send it to one of the other members of the team to see if he can get any further with it.
But as Billy said, how long has it been going? The fact that it has that many steps suggests that it's quite a big WU using the new GBGromacs core. It might just be taking a long time, but then again that core hasn't been around for long so there may still be some minor niggles with it.
Can you upload your FahLog.txt and link us to it?
Failing that, it might just be an issue with the WU. You might be able to send it to one of the other members of the team to see if he can get any further with it.
But as Billy said, how long has it been going? The fact that it has that many steps suggests that it's quite a big WU using the new GBGromacs core. It might just be taking a long time, but then again that core hasn't been around for long so there may still be some minor niggles with it.
Can you upload your FahLog.txt and link us to it?
Tell us what project it's working on - some can take quite a long time between frames and with the default level of reporting it will look like it's doing nothing
it will only report in the log when it's done 1% of the WU - in your case that's every 1250000 steps - so the fact it doesn't look like it's doing anything isn't something to worry about
The WUs in folding@home more often than not last days rather than hours, they used to be a lot shorter but then you had to contact the servers a lot more often (and waste good crunching time)
As Mattus says just make sure the program is using the CPU rather than something else - it's the core rather than the client that uses the CPU so just look for FahCore_xx.exe (xx being numbers/letters depending on the sort of work you have) using up to 99% of the CPU and you should be fine
it will only report in the log when it's done 1% of the WU - in your case that's every 1250000 steps - so the fact it doesn't look like it's doing anything isn't something to worry about
The WUs in folding@home more often than not last days rather than hours, they used to be a lot shorter but then you had to contact the servers a lot more often (and waste good crunching time)
As Mattus says just make sure the program is using the CPU rather than something else - it's the core rather than the client that uses the CPU so just look for FahCore_xx.exe (xx being numbers/letters depending on the sort of work you have) using up to 99% of the CPU and you should be fine
Well how's it doing, Iso? Have you diagnosed it as normal or have you given up?