LeonardoWake up and smell the glaciersEagle River, AlaskaIcrontian
edited March 2007
I'm at work right now, so I'm not going to analyze the details. That screen shot was not from the computer from which I was writing, but was from a machine that was doing nothing but running Folding. So, suffice it to say that Folding was requiring somewhere between 400 to 500(+) MB of physical memory.
I like the points. Just saw my first 1760 come through. It took a long time to show in the point count.
I am running a fairly striped down w2k install. Memory usage shows as 500k, my OS is less than 200k of that.
0
LeonardoWake up and smell the glaciersEagle River, AlaskaIcrontian
edited March 2007
It took a long time to show in the point count.
The points counts are taking much longer now because of all the new initiatives involved with Windows SMP and PS3.
Some of them are hashed up a lot more than that.
My C2D box shut down last night, it doesn't like any power disruption, like turning the lights off.
This morning it resumed just fine.
Finally I am back to making some points. My production has been in the tank for the last two weeks. The huge WUs now make it tough to get back into steady output.
Ok so it's ok then. The interval is set at 15 minutes if i remember correctly. Don't recall changing it.
The wu is at 18% and completing a frame every 26 minutes. That reminds me about the 346 pointers of regular wu that needed 3 days to complete at 50 mins a frame and now i have another 1K points in a day or 2. :bigggrin:
Edit
I forgot. Just how long does it take after a smp wu is completed before you can see the results? It's been like 3 days before my first smp wu was done yet my points hasn't changed.
Some of them are hashed up a lot more than that.
My C2D box shut down last night, it doesn't like any power disruption, like turning the lights off.
This morning it resumed just fine.
Finally I am back to making some points. My production has been in the tank for the last two weeks. The huge WUs now make it tough to get back into steady output.
I must have missed some points then because as you said eoc showed the points.
0
LeonardoWake up and smell the glaciersEagle River, AlaskaIcrontian
edited March 2007
The updates are only posted three times daily now, if I'm correct. Check your logs. If your computer uploaded the completed work units, you should have received credit.
Only? Didn't know how often it updated before. I used to check my sig to see if the points had increased and it hadn't until today hence why o worried. I do check the logs just so i will know what the client does.
Ok now i'm angry. The client has been trying all day to download wus but failed each time. What is going on? :sad2:
0
LeonardoWake up and smell the glaciersEagle River, AlaskaIcrontian
edited March 2007
Would you please post a log. Also, have you installed, as a separate download, .Net Framework 2.0? Concerning 2.0 Framework, do not assume that a previous Windows update is sufficient. I had to install install it on one of my machines, even though it had been installed a while back through Windows Updates.
Hey leo if you had seen my previous posts you would know that i have already folded 3 wus with the smp so it has been working until now which makes me think that something is up with the assignment server.
But if you want a log then here's one. Not that i think it will help. It usually doesn't take more than a couple of hours before the client gets a new wu but now it's been more than 12.
[16:27:12] + Attempting to get work packet
[16:27:12] - Connecting to assignment server
[16:27:13] - Successful: assigned to (171.64.65.64).
[16:27:13] + News From Folding@Home: Welcome to Folding@Home
[16:27:13] Loaded queue successfully.
[17:07:18] + Could not get Work unit data from Work Server
[17:07:18] - Error: Attempt #12 to get work failed, and no other work to do.
Waiting before retry.
[17:55:24] + Attempting to get work packet
[17:55:24] - Connecting to assignment server
[17:55:25] - Successful: assigned to (171.64.65.64).
[17:55:25] + News From Folding@Home: Welcome to Folding@Home
[17:55:25] Loaded queue successfully.
[18:35:30] + Could not get Work unit data from Work Server
[18:35:30] - Error: Attempt #13 to get work failed, and no other work to do.
Waiting before retry.
[19:23:37] + Attempting to get work packet
[19:23:37] - Connecting to assignment server
[19:23:38] - Successful: assigned to (171.64.65.64).
[19:23:38] + News From Folding@Home: Welcome to Folding@Home
[19:23:38] Loaded queue successfully.
Maybe I'm wrong about the terminology, but I thought "standard loops" meant that it wasn't running with SSE on. Have you tried running it with the -forceasm flag? The FAQ recommends it, and it saved me from dumping a WU once.
Since you asked for recommendations, I recommend you OC your A64 a bit more. You know, for science
I just got home and checked my log - for project 2610 it took me 32.5 minutes/frame. My Opty is running at 2475 Mhz, so I suppose 40 min/frame on a 2000 Mhz is about right.
Just to reiterate, I would definitely advise using -forceasm, not just because a lack of optimizations might be slowing you down (if not now, it might later), but it helped me recover from an error that crashed the folding cores once.
0
LeonardoWake up and smell the glaciersEagle River, AlaskaIcrontian
edited April 2007
It is running proj 2610 and taking about 40 min/frame. Does this sound right?
If that's an AMD dual core at 2000MHz with 1GB DRAM, 40 minutes/frame sounds about right.
If it's a Core 2 Duo at 2GHz with 1GB DRAM, it should be about 29-30min/frame. [EDIT: OK, so I was WAY off on this estimate!]
Comments
I am running a fairly striped down w2k install. Memory usage shows as 500k, my OS is less than 200k of that.
That explains why i haven't seen my points move. I was beginning to think that i typed in the wrong name.
[11:07:20] - Starting from initial work packet
[11:07:20]
[11:07:20] Project: 2652 (Run 0, Clone 232, Gen 6)
[11:07:20]
[11:07:21] Assembly optimizations on if available.
[11:07:21] Entering M.D.
[11:07:38] ial work packet
[11:07:38]
[11:07:38] Project: 2652 (Run 0, Clone 232, Gen 6)
[11:07:38]
[11:07:38] 652 (Run 0, Clone 232, Gen 6)
[11:07:38]
[11:07:38] Entering M.D.
[11:07:44] Rejecting checkpoint
[11:07:45] Protein: Protein
[11:07:45] Writing local files
[11:07:46] Extra SSE boost OK.
[11:07:46] Writing local files
[11:07:46] Completed 0 out of 1000000 steps (0 percent)
I'll post back if i see any more strange things.
I see your concern but I don't think it's anything to worry about. What is your checkpoint interval setting in the config?
My C2D box shut down last night, it doesn't like any power disruption, like turning the lights off.
This morning it resumed just fine.
Finally I am back to making some points. My production has been in the tank for the last two weeks. The huge WUs now make it tough to get back into steady output.
The wu is at 18% and completing a frame every 26 minutes. That reminds me about the 346 pointers of regular wu that needed 3 days to complete at 50 mins a frame and now i have another 1K points in a day or 2. :bigggrin:
Edit
I forgot. Just how long does it take after a smp wu is completed before you can see the results? It's been like 3 days before my first smp wu was done yet my points hasn't changed.
Sounds like you should get an UPS.
But if you want a log then here's one. Not that i think it will help. It usually doesn't take more than a couple of hours before the client gets a new wu but now it's been more than 12.
[16:27:12] + Attempting to get work packet
[16:27:12] - Connecting to assignment server
[16:27:13] - Successful: assigned to (171.64.65.64).
[16:27:13] + News From Folding@Home: Welcome to Folding@Home
[16:27:13] Loaded queue successfully.
[17:07:18] + Could not get Work unit data from Work Server
[17:07:18] - Error: Attempt #12 to get work failed, and no other work to do.
Waiting before retry.
[17:55:24] + Attempting to get work packet
[17:55:24] - Connecting to assignment server
[17:55:25] - Successful: assigned to (171.64.65.64).
[17:55:25] + News From Folding@Home: Welcome to Folding@Home
[17:55:25] Loaded queue successfully.
[18:35:30] + Could not get Work unit data from Work Server
[18:35:30] - Error: Attempt #13 to get work failed, and no other work to do.
Waiting before retry.
[19:23:37] + Attempting to get work packet
[19:23:37] - Connecting to assignment server
[19:23:38] - Successful: assigned to (171.64.65.64).
[19:23:38] + News From Folding@Home: Welcome to Folding@Home
[19:23:38] Loaded queue successfully.
My X1950pro was thrashing and not getting much done.
It is running proj 2610 and taking about 40 min/frame. Does this sound right?
I have std loops, extra SSE boost.
It does seem slow. My E6300 is running 20min/frame.
Any other thoughts?
Since you asked for recommendations, I recommend you OC your A64 a bit more. You know, for science
Just to reiterate, I would definitely advise using -forceasm, not just because a lack of optimizations might be slowing you down (if not now, it might later), but it helped me recover from an error that crashed the folding cores once.
If it's a Core 2 Duo at 2GHz with 1GB DRAM, it should be about 29-30min/frame. [EDIT: OK, so I was WAY off on this estimate!]
Pentium D9xx at 4GHz is 18-19min per
C2D @ 3GHz is about 14min per
AX2, 200x10 = 2.0GHz, 2GB ram, 39 min/frame
C2D, 275x7 = 1.925GHz, 2GB ram, 21 min/frame
Maybe I should shop for some faster CPUs