I've a PIII as well and it happens to get all the long WUs :-).
Have you considered letting it crunch under Linux? Gary Roberts made some experiments comparing PIIIs under Linux and Windows see here and demonstrated that the Linux app takes 30% less time per WU.
I must admit I'm disappointed with the short deadlines. I travel a lot, so I can only crunch on my portable nowadays. The deadline for this last WU is coming very close, and while I will finish, I've had to leave the notebook up overnight once. I'm loathe to do this because of the lifetimes built into various components I can't replace, and I really feel crunching on my notebook should be a background task.
Worse, Einstein keeps complaining my CPU is only active 21% or so and it gets 50% of that, so it won't give more than one unit. SETI has been up and down recently. Coupled with the spotty connections I get from living a traveling life, my work cache dries up and I'm not running efficiently. However, attaching to a third project will just give Einstein more complaint.
In short, I'm afraid Einstein is demanding too much of users like myself, and this project will regrettably have to be left to the power crunchers. I'll be detaching after this WU finishes. I liked donating spare CPU time to this worthy goal, but I just can't make the deadlines.
I must admit I'm disappointed with the short deadlines. I travel a lot, so I can only crunch on my portable nowadays. The deadline for this last WU is coming very close, and while I will finish, I've had to leave the notebook up overnight once. I'm loathe to do this because of the lifetimes built into various components I can't replace, and I really feel crunching on my notebook should be a background task.
Worse, Einstein keeps complaining my CPU is only active 21% or so and it gets 50% of that, so it won't give more than one unit. SETI has been up and down recently. Coupled with the spotty connections I get from living a traveling life, my work cache dries up and I'm not running efficiently. However, attaching to a third project will just give Einstein more complaint.
In short, I'm afraid Einstein is demanding too much of users like myself, and this project will regrettably have to be left to the power crunchers. I'll be detaching after this WU finishes. I liked donating spare CPU time to this worthy goal, but I just can't make the deadlines.
If you have to give up on Einstein perhaps you could try Rosetta. The work unit run times there are completely up to the user - you can do as short as 2 hours or as long as 24.
In short, I'm afraid Einstein is demanding too much of users like myself, and this project will regrettably have to be left to the power crunchers. I'll be detaching after this WU finishes. I liked donating spare CPU time to this worthy goal, but I just can't make the deadlines.
Granted the work is tough, demanding, and downright frustrating at times at the moment, but we're trying out a whole new approach to the analysis of the interferometer data on S5R2. Probably better to just suspend the project for now rather than detach if you're finding the current work is not to your runtime style. The app is almost certain to get better before too much longer from a reliability and performance POV if history is any indication. That will go a long way to relieving some of the deadline pressure.
However based in my data, the project is most likely going to have to look at a deadline increase no matter what or risk losing participants due to the 'tightness' factor.
(I hope it will validate or the owner might be really frustrated, it currently sticks at "Checked, but no consensus yet", Linux vs. Windows)
I hope he's a patient type, with a machine like that.
The resend has gone to a Windows box (bad news), but it's a Windows box with zero credit after 6 months and an average turnround of 14 days! I fear yet another resend is in the offing.
(I hope it will validate or the owner might be really frustrated, it currently sticks at "Checked, but no consensus yet", Linux vs. Windows)
I hope he's a patient type, with a machine like that.
The resend has gone to a Windows box (bad news), but it's a Windows box with zero credit after 6 months and an average turnround of 14 days! I fear yet another resend is in the offing.
I guess a Pentium MMX will mark the absolute minimum for E@H. If you compute a (Credits / kilo watts* hour) ratio, the energy efficiency must be quite catastrophic :-)
I think all PI-MMX's are going to be hard pressed to meet any but the lowest template frequency WU's at this point, based on what my K6's have done even taking into account the stronger FPU's in them. Assuming the project team can roughly half the runtime once they optimize it should open them up to a wider range of frequencies, but if the deadline stays at two weeks EAH will be a very tight deadline project for them.
Later K6-2/3's and Deschutes PII's should be fairly workable on low template frequencies and the shorter high band one's. P-III's and Athlons up should still be in pretty good shape ultimately.
My PII Deschutes running Linux has just completed a QMC@home WU which took 283 CPU hours and received 551 credits, that is about 2 credits/hour. Einstein is more generous. Now my next deadline with Einstein is May 30 and with SETI June 11. I should barely meet Einstein's deadline, SETI's is much easier.
Tullio
I just finished a long unit
)
I just finished a long unit on a 450MHz P3.... 862,000 seconds 8)
http://einsteinathome.org/task/84201239
RE: I just finished a long
)
I've a PIII as well and it happens to get all the long WUs :-).
Have you considered letting it crunch under Linux? Gary Roberts made some experiments comparing PIIIs under Linux and Windows see here and demonstrated that the Linux app takes 30% less time per WU.
I guess the situation will be smilar for K7 AMDs.
CU
BRM
I must admit I'm disappointed
)
I must admit I'm disappointed with the short deadlines. I travel a lot, so I can only crunch on my portable nowadays. The deadline for this last WU is coming very close, and while I will finish, I've had to leave the notebook up overnight once. I'm loathe to do this because of the lifetimes built into various components I can't replace, and I really feel crunching on my notebook should be a background task.
Worse, Einstein keeps complaining my CPU is only active 21% or so and it gets 50% of that, so it won't give more than one unit. SETI has been up and down recently. Coupled with the spotty connections I get from living a traveling life, my work cache dries up and I'm not running efficiently. However, attaching to a third project will just give Einstein more complaint.
In short, I'm afraid Einstein is demanding too much of users like myself, and this project will regrettably have to be left to the power crunchers. I'll be detaching after this WU finishes. I liked donating spare CPU time to this worthy goal, but I just can't make the deadlines.
RE: I must admit I'm
)
If you have to give up on Einstein perhaps you could try Rosetta. The work unit run times there are completely up to the user - you can do as short as 2 hours or as long as 24.
RE: In short, I'm afraid
)
Granted the work is tough, demanding, and downright frustrating at times at the moment, but we're trying out a whole new approach to the analysis of the interferometer data on S5R2. Probably better to just suspend the project for now rather than detach if you're finding the current work is not to your runtime style. The app is almost certain to get better before too much longer from a reliability and performance POV if history is any indication. That will go a long way to relieving some of the deadline pressure.
However based in my data, the project is most likely going to have to look at a deadline increase no matter what or risk losing participants due to the 'tightness' factor.
Alinator
Alinator
Just saw this one :
)
Just saw this one : resultid=83946927
CPU time 1171511.101237 (that's nearly 2 weeks !!!)
CPU type GenuineIntel Pentium MMX
One day past the deadline but still accepted by the server
(I hope it will validate or the owner might be really frustrated, it currently sticks at "Checked, but no consensus yet", Linux vs. Windows)
RE: (I hope it will
)
I hope he's a patient type, with a machine like that.
The resend has gone to a Windows box (bad news), but it's a Windows box with zero credit after 6 months and an average turnround of 14 days! I fear yet another resend is in the offing.
RE: RE: (I hope it will
)
I guess a Pentium MMX will mark the absolute minimum for E@H. If you compute a (Credits / kilo watts* hour) ratio, the energy efficiency must be quite catastrophic :-)
CU
BRM
I think all PI-MMX's are
)
I think all PI-MMX's are going to be hard pressed to meet any but the lowest template frequency WU's at this point, based on what my K6's have done even taking into account the stronger FPU's in them. Assuming the project team can roughly half the runtime once they optimize it should open them up to a wider range of frequencies, but if the deadline stays at two weeks EAH will be a very tight deadline project for them.
Later K6-2/3's and Deschutes PII's should be fairly workable on low template frequencies and the shorter high band one's. P-III's and Athlons up should still be in pretty good shape ultimately.
Alinator
My PII Deschutes running
)
My PII Deschutes running Linux has just completed a QMC@home WU which took 283 CPU hours and received 551 credits, that is about 2 credits/hour. Einstein is more generous. Now my next deadline with Einstein is May 30 and with SETI June 11. I should barely meet Einstein's deadline, SETI's is much easier.
Tullio