NB for anyone else wanting to do any testing - have a look at the server status page first. While the "Oldest Unsent Result" is at 8 days or more (creation time of 12:40 on Monday 17 September), you'll probably be getting S5R2 work.
Which is also the reason for the astronomical predicted length of S5R3 on the status page. Most crunching is still done on S5R2, so progress on S5R3 is slow. This will change once the S5R2 pool is completely drained.
NB for anyone else wanting to do any testing - have a look at the server status page first. While the "Oldest Unsent Result" is at 8 days or more (creation time of 12:40 on Monday 17 September), you'll probably be getting S5R2 work.
I think it knows what it has sent you. If there is more S5R2 work it would have tried to send you had you done nothing, it just realizes some files are missing and resends them, rather than treating that as a reason to start you a though your were fresh.
I think it knows what it has sent you. If there is more S5R2 work it would have tried to send you had you done nothing, it just realizes some files are missing and resends them, rather than treating that as a reason to start you a though your were fresh.
No, this was a brand new send - I hand-edited client_state.xml to get rid of the old references. I got:
25/09/2007 12:37:37|Einstein@Home|Sending scheduler request: Requested by user
25/09/2007 12:37:37|Einstein@Home|Requesting 87162 seconds of new work
25/09/2007 12:37:42|Einstein@Home|Scheduler RPC succeeded [server version 601]
25/09/2007 12:37:42|Einstein@Home|Deferring communication for 1 min 0 sec
25/09/2007 12:37:42|Einstein@Home|Reason: requested by project
25/09/2007 12:37:44|Einstein@Home|[file_xfer] Started download of file einstein_S5R2_4.38_windows_intelx86.exe
25/09/2007 12:37:44|Einstein@Home|[file_xfer] Started download of file einstein_S5R2_4.38_windows_intelx86.pdb
25/09/2007 12:38:12|Einstein@Home|[file_xfer] Finished download of file einstein_S5R2_4.38_windows_intelx86.exe
25/09/2007 12:38:12|Einstein@Home|[file_xfer] Throughput 119560 bytes/sec
25/09/2007 12:38:12|Einstein@Home|[file_xfer] Started download of file h1_0543.00_S5R2
25/09/2007 12:38:20|Einstein@Home|[file_xfer] Finished download of file einstein_S5R2_4.38_windows_intelx86.pdb
25/09/2007 12:38:20|Einstein@Home|[file_xfer] Throughput 122342 bytes/sec
25/09/2007 12:38:20|Einstein@Home|[file_xfer] Started download of file l1_0543.00_S5R2
25/09/2007 12:38:41|Einstein@Home|[file_xfer] Finished download of file h1_0543.00_S5R2
25/09/2007 12:38:41|Einstein@Home|[file_xfer] Throughput 122296 bytes/sec
25/09/2007 12:38:41|Einstein@Home|[file_xfer] Started download of file h1_0543.05_S5R2
25/09/2007 12:38:47|Einstein@Home|[file_xfer] Finished download of file l1_0543.00_S5R2
25/09/2007 12:38:47|Einstein@Home|[file_xfer] Throughput 123010 bytes/sec
25/09/2007 12:38:47|Einstein@Home|[file_xfer] Started download of file l1_0543.05_S5R2
25/09/2007 12:39:10|Einstein@Home|[file_xfer] Finished download of file h1_0543.05_S5R2
25/09/2007 12:39:10|Einstein@Home|[file_xfer] Throughput 123500 bytes/sec
25/09/2007 12:39:10|Einstein@Home|[file_xfer] Started download of file h1_0543.10_S5R2
25/09/2007 12:39:14|Einstein@Home|[file_xfer] Finished download of file l1_0543.05_S5R2
25/09/2007 12:39:14|Einstein@Home|[file_xfer] Throughput 123231 bytes/sec
25/09/2007 12:39:14|Einstein@Home|[file_xfer] Started download of file l1_0543.10_S5R2
25/09/2007 12:39:39|Einstein@Home|[file_xfer] Finished download of file h1_0543.10_S5R2
25/09/2007 12:39:39|Einstein@Home|[file_xfer] Throughput 122695 bytes/sec
25/09/2007 12:39:39|Einstein@Home|[file_xfer] Started download of file h1_0543.15_S5R2
25/09/2007 12:39:41|Einstein@Home|[file_xfer] Finished download of file l1_0543.10_S5R2
25/09/2007 12:39:41|Einstein@Home|[file_xfer] Throughput 122359 bytes/sec
25/09/2007 12:39:41|Einstein@Home|[file_xfer] Started download of file l1_0543.15_S5R2
25/09/2007 12:40:09|Einstein@Home|[file_xfer] Finished download of file h1_0543.15_S5R2
25/09/2007 12:40:09|Einstein@Home|[file_xfer] Throughput 123500 bytes/sec
25/09/2007 12:40:09|Einstein@Home|[file_xfer] Finished download of file l1_0543.15_S5R2
25/09/2007 12:40:09|Einstein@Home|[file_xfer] Throughput 118708 bytes/sec
25/09/2007 12:40:09|Einstein@Home|[file_xfer] Started download of file h1_0543.20_S5R2
25/09/2007 12:40:09|Einstein@Home|[file_xfer] Started download of file l1_0543.20_S5R2
25/09/2007 12:40:38|Einstein@Home|[file_xfer] Finished download of file l1_0543.20_S5R2
25/09/2007 12:40:38|Einstein@Home|[file_xfer] Throughput 119599 bytes/sec
25/09/2007 12:40:39|Einstein@Home|[file_xfer] Finished download of file h1_0543.20_S5R2
25/09/2007 12:40:39|Einstein@Home|[file_xfer] Throughput 125137 bytes/sec
- no trace of a resend.
This box has only ever done 532.xx and 523.xx work using Beta v4.40 previously, newly built and attached to Einstein less than a month ago.
I assumed the server as well as client_state.xml had a record of what you were "supposed" to have. Long ago I deleted "just about" everything Einstein in an effort to get away from a batch of results that for over a month had kept one of my machines tied up processing work it was particularly ill suited to. That time I got the same work right back--but I'm sure I did not edit client_state.xml (I only got brave enough to do that more recently), and not sure that I deleted it either.
Since Bruce asked for observations on the 'early release' S5R3, to help fine-tune the bulk run later, here's another one to fill in the time while we're waiting for the last of the S5R2s to be issued.
Host 1001562 is working it's way down through an almost consecutive run from the 522.10 set - I've reported 168 thru 162 so far, and I've got most of 161 thru 150 in stock. There's been a very steady decrease in crunching time as I've gone through them, averaging about 1% per WU, and since the credit claim has been static (218.66 every time), a corresponding steady increase in the rate of return. Could that account for the wide variations people have been reporting?
Edit - I've got the same wingman (989567) for all of them, and his run is even more complete than mine. Results are only just starting to come in, but early indications are that it's the same pattern. He's running Linux on AMD against my WIntel, so might be a useful pairing to keep an eye on.
Since Bruce asked for observations on the 'early release' S5R3, to help fine-tune the bulk run later, here's another one to fill in the time while we're waiting for the last of the S5R2s to be issued.
Host 1001562 is working it's way down through an almost consecutive run from the 522.10 set - I've reported 168 thru 162 so far, and I've got most of 161 thru 150 in stock. There's been a very steady decrease in crunching time as I've gone through them, averaging about 1% per WU, and since the credit claim has been static (218.66 every time), a corresponding steady increase in the rate of return. Could that account for the wide variations people have been reporting?
Edit - I've got the same wingman (989567) for all of them, and his run is even more complete than mine. Results are only just starting to come in, but early indications are that it's the same pattern. He's running Linux on AMD against my WIntel, so might be a useful pairing to keep an eye on.
You wingman is processing
h1_0522.05_S5R2__35_S5R2c in 87,063.38 Sec. and gets 461.04 credits but
h1_0522.10_S5R2__171_S5R3a in 71,280.50 Sec. gives him only 218.66 credits!
That's 188,84 sec./credit against 325,99 sec./credit.
It looks like my AMD 6000+ machine is taking a bit of a performance hit with the S5R3's. They're taking just a bit over half as long to do as it would a monster S5R2, but only giving me about one-third of the credit.
This box is running Kubuntu 7.04 Linux. I would be interesting if I could have a Windows setup with the same hardware to make a comparison.
It looks like my AMD 6000+ machine is taking a bit of a performance hit with the S5R3's. They're taking just a bit over half as long to do as it would a monster S5R2, but only giving me about one-third of the credit.
This box is running Kubuntu 7.04 Linux.
Two comments on your experience.
1. Of your three S5R3 results, one has successful quorum partner--a Core 2 Duo running XP. That person saw about a 3% degradation from their S5R2 resuls on your worst (slowest) result, much less degradation than you report.
2. Your experience is another example of strong CPU time variation for results in the same series with the same credit:
all three results are of the form h1_0545.10_S5R2__rrr_S5R3a_n
RE: NB for anyone else
)
Which is also the reason for the astronomical predicted length of S5R3 on the status page. Most crunching is still done on S5R2, so progress on S5R3 is slow. This will change once the S5R2 pool is completely drained.
CU
Bikeman
RE: NB for anyone else
)
I think it knows what it has sent you. If there is more S5R2 work it would have tried to send you had you done nothing, it just realizes some files are missing and resends them, rather than treating that as a reason to start you a though your were fresh.
RE: I think it knows what
)
No, this was a brand new send - I hand-edited client_state.xml to get rid of the old references. I got:
25/09/2007 12:37:37|Einstein@Home|Sending scheduler request: Requested by user
25/09/2007 12:37:37|Einstein@Home|Requesting 87162 seconds of new work
25/09/2007 12:37:42|Einstein@Home|Scheduler RPC succeeded [server version 601]
25/09/2007 12:37:42|Einstein@Home|Deferring communication for 1 min 0 sec
25/09/2007 12:37:42|Einstein@Home|Reason: requested by project
25/09/2007 12:37:44|Einstein@Home|[file_xfer] Started download of file einstein_S5R2_4.38_windows_intelx86.exe
25/09/2007 12:37:44|Einstein@Home|[file_xfer] Started download of file einstein_S5R2_4.38_windows_intelx86.pdb
25/09/2007 12:38:12|Einstein@Home|[file_xfer] Finished download of file einstein_S5R2_4.38_windows_intelx86.exe
25/09/2007 12:38:12|Einstein@Home|[file_xfer] Throughput 119560 bytes/sec
25/09/2007 12:38:12|Einstein@Home|[file_xfer] Started download of file h1_0543.00_S5R2
25/09/2007 12:38:20|Einstein@Home|[file_xfer] Finished download of file einstein_S5R2_4.38_windows_intelx86.pdb
25/09/2007 12:38:20|Einstein@Home|[file_xfer] Throughput 122342 bytes/sec
25/09/2007 12:38:20|Einstein@Home|[file_xfer] Started download of file l1_0543.00_S5R2
25/09/2007 12:38:41|Einstein@Home|[file_xfer] Finished download of file h1_0543.00_S5R2
25/09/2007 12:38:41|Einstein@Home|[file_xfer] Throughput 122296 bytes/sec
25/09/2007 12:38:41|Einstein@Home|[file_xfer] Started download of file h1_0543.05_S5R2
25/09/2007 12:38:47|Einstein@Home|[file_xfer] Finished download of file l1_0543.00_S5R2
25/09/2007 12:38:47|Einstein@Home|[file_xfer] Throughput 123010 bytes/sec
25/09/2007 12:38:47|Einstein@Home|[file_xfer] Started download of file l1_0543.05_S5R2
25/09/2007 12:39:10|Einstein@Home|[file_xfer] Finished download of file h1_0543.05_S5R2
25/09/2007 12:39:10|Einstein@Home|[file_xfer] Throughput 123500 bytes/sec
25/09/2007 12:39:10|Einstein@Home|[file_xfer] Started download of file h1_0543.10_S5R2
25/09/2007 12:39:14|Einstein@Home|[file_xfer] Finished download of file l1_0543.05_S5R2
25/09/2007 12:39:14|Einstein@Home|[file_xfer] Throughput 123231 bytes/sec
25/09/2007 12:39:14|Einstein@Home|[file_xfer] Started download of file l1_0543.10_S5R2
25/09/2007 12:39:39|Einstein@Home|[file_xfer] Finished download of file h1_0543.10_S5R2
25/09/2007 12:39:39|Einstein@Home|[file_xfer] Throughput 122695 bytes/sec
25/09/2007 12:39:39|Einstein@Home|[file_xfer] Started download of file h1_0543.15_S5R2
25/09/2007 12:39:41|Einstein@Home|[file_xfer] Finished download of file l1_0543.10_S5R2
25/09/2007 12:39:41|Einstein@Home|[file_xfer] Throughput 122359 bytes/sec
25/09/2007 12:39:41|Einstein@Home|[file_xfer] Started download of file l1_0543.15_S5R2
25/09/2007 12:40:09|Einstein@Home|[file_xfer] Finished download of file h1_0543.15_S5R2
25/09/2007 12:40:09|Einstein@Home|[file_xfer] Throughput 123500 bytes/sec
25/09/2007 12:40:09|Einstein@Home|[file_xfer] Finished download of file l1_0543.15_S5R2
25/09/2007 12:40:09|Einstein@Home|[file_xfer] Throughput 118708 bytes/sec
25/09/2007 12:40:09|Einstein@Home|[file_xfer] Started download of file h1_0543.20_S5R2
25/09/2007 12:40:09|Einstein@Home|[file_xfer] Started download of file l1_0543.20_S5R2
25/09/2007 12:40:38|Einstein@Home|[file_xfer] Finished download of file l1_0543.20_S5R2
25/09/2007 12:40:38|Einstein@Home|[file_xfer] Throughput 119599 bytes/sec
25/09/2007 12:40:39|Einstein@Home|[file_xfer] Finished download of file h1_0543.20_S5R2
25/09/2007 12:40:39|Einstein@Home|[file_xfer] Throughput 125137 bytes/sec
- no trace of a resend.
This box has only ever done 532.xx and 523.xx work using Beta v4.40 previously, newly built and attached to Einstein less than a month ago.
My first S5R3 WU just
)
My first S5R3 WU just finished on P4-2.8E (with HT):
name: h1_0539.05_S5R2__158_S5R3a
cpu time: 114,452.47 secs
granted credit: 219.42 pts
so it's about 13.8 pts/hr.
To compared with S5R2...
name: h1_0539.05_S5R2__59_S5R2c
cpu time: 313,573.23 secs
granted credit: 646.69 pts
it's about 14.8 pts/hr.
Welcome To Team China!
Results for PPC Mac G4 1.25
)
Results for PPC Mac G4 1.25 GHz:
R3: 97,902.35 sec, 219.42 cr = 8.068 cr/hr
R2: 217,336.68 sec, 633.91 cr = 10.500 cr/hr
R2: 159,106.92 sec, 472.32 cr = 10.686 cr/hr
R2 avg: 10.593 cr/hr
So about a 25% drop in credit for R3 vs. R2. Ouch.
RE: - no trace of a
)
I stand corrected. Thanks.
I assumed the server as well as client_state.xml had a record of what you were "supposed" to have. Long ago I deleted "just about" everything Einstein in an effort to get away from a batch of results that for over a month had kept one of my machines tied up processing work it was particularly ill suited to. That time I got the same work right back--but I'm sure I did not edit client_state.xml (I only got brave enough to do that more recently), and not sure that I deleted it either.
Since Bruce asked for
)
Since Bruce asked for observations on the 'early release' S5R3, to help fine-tune the bulk run later, here's another one to fill in the time while we're waiting for the last of the S5R2s to be issued.
Host 1001562 is working it's way down through an almost consecutive run from the 522.10 set - I've reported 168 thru 162 so far, and I've got most of 161 thru 150 in stock. There's been a very steady decrease in crunching time as I've gone through them, averaging about 1% per WU, and since the credit claim has been static (218.66 every time), a corresponding steady increase in the rate of return. Could that account for the wide variations people have been reporting?
Edit - I've got the same wingman (989567) for all of them, and his run is even more complete than mine. Results are only just starting to come in, but early indications are that it's the same pattern. He's running Linux on AMD against my WIntel, so might be a useful pairing to keep an eye on.
RE: Since Bruce asked for
)
You wingman is processing
h1_0522.05_S5R2__35_S5R2c in 87,063.38 Sec. and gets 461.04 credits but
h1_0522.10_S5R2__171_S5R3a in 71,280.50 Sec. gives him only 218.66 credits!
That's 188,84 sec./credit against 325,99 sec./credit.
Udo
![](http://boinc.mundayweb.com/one/stats.php/userID:2059/.png)
Well folks, It looks like
)
Well folks,
It looks like my AMD 6000+ machine is taking a bit of a performance hit with the S5R3's. They're taking just a bit over half as long to do as it would a monster S5R2, but only giving me about one-third of the credit.
This box is running Kubuntu 7.04 Linux. I would be interesting if I could have a Windows setup with the same hardware to make a comparison.
Ciao,
Donnie
RE: It looks like my AMD
)
Two comments on your experience.
1. Of your three S5R3 results, one has successful quorum partner--a Core 2 Duo running XP. That person saw about a 3% degradation from their S5R2 resuls on your worst (slowest) result, much less degradation than you report.
2. Your experience is another example of strong CPU time variation for results in the same series with the same credit:
all three results are of the form h1_0545.10_S5R2__rrr_S5R3a_n
Res CPU_______credit
185 57,125.42 220.28
178 52,348.26 220.28
174 50,046.86 220.28