// DBOINCP-300: added node comment count condition in order to get Preview working ?>
xi3piscium
Joined: 13 Dec 05
Posts: 55
Credit: 30088
RAC: 0
17 Jun 2006 9:24:16 UTC
Topic 191399
(moderation:
)
I just recieved my first batch of S5 wu's. I'm looking at an ETC of 23hrs on the wu that is crunching as I write, iMac G5 PPC 1.9Ghz 1.0Gb RAM. Unix CLI 5.4.9
Bernd said: To make up for the faster Apps we increased the size of the workunits. The "long" ones will be roughly five times as long as the "long" ones from S4, the "short" ones will be roughly twice as long as their S4 counterparts.
My first long S5 WU completes in 19 hours which is 9.5x longer (measured in time) than the long S4 WU which takes me 2 hours using Akos S39L. This raises my eyebrow! Maybe these WUs are a little too long and/or the app isn't fast enough or cpu specific enough. I'm using Intel P4 3GHz/HT on and 100% EaH. I think the small L1 cache must come into play on my machine. Like someone else said, I can live with any size WU, but I "feel" more comfortable with shorter run times. I will go with the flow, however.
Bernd said: To make up for the faster Apps we increased the size of the workunits. The "long" ones will be roughly five times as long as the "long" ones from S4, the "short" ones will be roughly twice as long as their S4 counterparts.
My first long S5 WU completes in 19 hours which is 9.5x longer (measured in time) than the long S4 WU which takes me 2 hours using Akos S39L. This raises my eyebrow! Maybe these WUs are a little too long and/or the app isn't fast enough or cpu specific enough. I'm using Intel P4 3GHz/HT on and 100% EaH. I think the small L1 cache must come into play on my machine. Like someone else said, I can live with any size WU, but I "feel" more comfortable with shorter run times. I will go with the flow, however.
This is only half the story though since the s5 app is ~3x faster than the stock s4 one. This means that the WUs will take about twice as long to complete at the momement. The s5 app is still being worked on to get it closer to akos's s4 speeds. Doing that will reduce the runtime to stock s4ish levels which is what the project apparently views as an optimal size.
14 hrs 42 mins for first S5 WU. This on an AMD XP 1600+ system.
Got 138.83 credit...works out to approx. 9.45 CS/hr
I can live with that. Mine has yet to be validated. Interesting that your claim (the lower of the two) was also what was granted.
Is it built into the valiadator to use the lower of the two when there are onlt two sent out? If I remember correct uFluids was doing it that way when they first started up. With two units averageing them seems to be the fairest, but as long as the same for all it is fair.
Ray
Crunch Time S5 Workunits
)
As your computer is hidden, we can't see WU name.
As you haven't provide WU name, we can only guess.
I would guess it's a longer one.
I have the same system as
)
I have the same system as yours, and my first S5 WU completed close to 11 hours.....
09:43:07 for the first one I
)
09:43:07 for the first one I got on an AMD XP 2800. I have a few others, but their turn hasn't come yet.
My first S5 workunit
)
My first S5 workunit (h1_0251.0_S5R1__11430_S5R1a) has completed in 1h19m on an AthlonXP 2100+ machine.
Welcome To Team China!
Bernd said: To make up for
)
Bernd said: To make up for the faster Apps we increased the size of the workunits. The "long" ones will be roughly five times as long as the "long" ones from S4, the "short" ones will be roughly twice as long as their S4 counterparts.
My first long S5 WU completes in 19 hours which is 9.5x longer (measured in time) than the long S4 WU which takes me 2 hours using Akos S39L. This raises my eyebrow! Maybe these WUs are a little too long and/or the app isn't fast enough or cpu specific enough. I'm using Intel P4 3GHz/HT on and 100% EaH. I think the small L1 cache must come into play on my machine. Like someone else said, I can live with any size WU, but I "feel" more comfortable with shorter run times. I will go with the flow, however.
RE: Bernd said: To make
)
This is only half the story though since the s5 app is ~3x faster than the stock s4 one. This means that the WUs will take about twice as long to complete at the momement. The s5 app is still being worked on to get it closer to akos's s4 speeds. Doing that will reduce the runtime to stock s4ish levels which is what the project apparently views as an optimal size.
RE: 09:43:07 for the first
)
14 hrs 42 mins for first S5 WU. This on an AMD XP 1600+ system.
Got 138.83 credit...works out to approx. 9.45 CS/hr
Seti Classic Final Total: 11446 WU.
RE: 14 hrs 42 mins for
)
I can live with that. Mine has yet to be validated. Interesting that your claim (the lower of the two) was also what was granted.
RE: RE: 14 hrs 42 mins
)
Is it built into the valiadator to use the lower of the two when there are onlt two sent out? If I remember correct uFluids was doing it that way when they first started up. With two units averageing them seems to be the fairest, but as long as the same for all it is fair.
Ray
Try the Pizza@Home project, good crunching.
RE: I can live with that.
)
Normally the host should claim the same credits, if I understand the new creditsystem right. Wondering about.
My first short S5: http://einsteinathome.org/task/34194416
53 minutes on a A64 3500+.