Just got a bunch of code 22 errors on my other linux box. Here's one example. Strange that my first box, with virtually identical equipment but a slightly different kernel, seems to chugging alone just fine.
Just got a bunch of code 22 errors on my other linux box. Here's one example. Strange that my first box, with virtually identical equipment but a slightly different kernel, seems to chugging alone just fine.
cpu time is always 0.00
With no CPU time this looks more like the usual 22 error that's described in the WIKI. Check that you have the 32Bit compatibility libraries installed. You had a couple of download errors on this box, maybe try to reset the project and download files from scratch. Also I've seen some problems with apparently non-existing files or directories with 5.10.x clients, which sometimes cure themselves without an apparent reason (and sometimes don't). I'm not using a 5.10 Client on any Linux box.
Sorry, could I get a link to the wiki page addressing this which hopefully includes command queries to identify misssing libraries and procedures to install 32 bit libraries in a 64 bit linux environment? Thanks.
Well I started processing these S5R3 Beta WU's to see if there was a speed up in processing time (and consequently an increase in granted credit).
S5R3 Application 4.02 started out at over 66,000 seconds, slowly reduced to a bit over 60,000 seconds. Then a sudden drop to between 52,570 to 50,065 seconds.
Credit started at just 12.02 cr/h rising to 15.96 cr/h (S5R2 gave me 21.4+ cr/h).
I then went to Beta as I was so disappointed with the new S5R3 Wu's.
S5R3 Application 4.09 started well, with the first 3 showing a great drop in processing times
40,307.92 seconds for WU 87374313
40,033.85 seconds for WU 87374374
43,621.74 seconds for WU 87375124
Giving credit of 19.82, 19.96, 18.32 cr/h for each one.
Unfortunately the next one has gone back to the same as the non Beta application with 52,867.22 seconds for WU 87376902
Dropping cr/h back to 15.11.
So S5R2 was giving (slowly dropping over the last few months) 24 cr/h reducing slowly to 21.43 with the last of the S5R2 work units.
S5R3 started giving me 12 and averaged out at 14.4 cr/h, a 32.76% Drop from S5R2.
First 3 Beta WU's gave me an average of 19.34 cr/h a 9.75% Drop from S5R2 but a 25.54% Increase over the first S5R3 WU's.
The last one is back to 29.49% Drop from S5R2 and only a 4.63% Increase over the first S5R3 WU's.
What happened to the speed up?
Forgot to mention that all my S5R3 WU's, including the Beta WU's and the last S5R2 that I did are all of the same 0518.05 frequency (on my AMD Opteron 285 Linux machine).
Your observations are consistent with other users' reports:
The variation of runtime in S5R3 is much higher than in S5R2. Hopefully this can be reflected in the future by a more fine grained credits allocation. Variation is routinely 20% and sometimes more.
On average, the new Linux beta app is much faster than the initial stock app, about 20 % on most machines.
Because the variation of runtime is in the same range as the speed-up, it can be expected that the slowest results from the new beta app are about as fast as the fastest results from the old stock app. On average they are still 20 % faster, and I think a 20 % improvement in speed is something of an achievement.
The staff are working on both: further closing the gap between Linux and Windows apps and a better prediction of runtime ==> more accurate credits. Stay tuned.
I just upgraded to the new Kubuntu 7.10 (okay, it's a bit before the release, but who cares- at least my sound works now) on my laptop, since it's working just fine I'm intending to be running Linux as my first OS now. So after running the first 2 WUs with the "normal" app to check that everyting is fine I'll be in for some Linux beta testing.
Yes, I've noticed those variations in runtime aswell. It's a real... let's say annoyance... for beta testing because it's very hard to tell if a new app is really faster or if one just had a shorter WU for the same credit. I'm suffering this problem on my desktop box atm, started using "EAH_NO_GRAPHICS" and it seems to be a little faster, but then, with only 2 WUs crunched after the change, it might still be within normal fluctuation...
I'm not worried about credit, that is going to equal out eventually, anyway (where is the difference between crunching to 50k sec WUs or one 40k and one 60k, in the end it's the same) but it's very hard to judge CPU and app performance if there is so much fluctuaction in the runtime/credit ratio. One has to collect quite a lot of examples before being able to say sth halfway definite.
Your observations are consistent with other users' reports:
The variation of runtime in S5R3 is much higher than in S5R2. Hopefully this can be reflected in the future by a more fine grained credits allocation. Variation is routinely 20% and sometimes more.
On average, the new Linux beta app is much faster than the initial stock app, about 20 % on most machines.
Because the variation of runtime is in the same range as the speed-up, it can be expected that the slowest results from the new beta app are about as fast as the fastest results from the old stock app. On average they are still 20 % faster, and I think a 20 % improvement in speed is something of an achievement.
The staff are working on both: further closing the gap between Linux and Windows apps and a better prediction of runtime ==> more accurate credits. Stay tuned.
CU
Bikeman
Hello Bikeman,
I have not noticed that Windows S5R3 is faster than S5R2 as my credit has dropped from a bit over 16 to about 14 now (AMD 4800+ Win XP). All it shows is that there has not been as big a drop as in the Linux application.
Just got a bunch of code 22
)
Just got a bunch of code 22 errors on my other linux box. Here's one example. Strange that my first box, with virtually identical equipment but a slightly different kernel, seems to chugging alone just fine.
cpu time is always 0.00
RE: Just got a bunch of
)
With no CPU time this looks more like the usual 22 error that's described in the WIKI. Check that you have the 32Bit compatibility libraries installed. You had a couple of download errors on this box, maybe try to reset the project and download files from scratch. Also I've seen some problems with apparently non-existing files or directories with 5.10.x clients, which sometimes cure themselves without an apparent reason (and sometimes don't). I'm not using a 5.10 Client on any Linux box.
BM
BM
Yup, and for a good reason.
)
Yup, and for a good reason. Note that 5.8.16 is still the recommended BOINC version for 32 bit Linux on Intel.
CU
Bikeman
EDIT: Unfortunately, there doesn't seem to be a "stable" BOINC for 64bit Linux on the BOINC download page.
Sorry, could I get a link to
)
Sorry, could I get a link to the wiki page addressing this which hopefully includes command queries to identify misssing libraries and procedures to install 32 bit libraries in a 64 bit linux environment? Thanks.
The WIKI I meant was what
)
The WIKI I meant was what ageless pointed to:
BM
BM
Not exactly the Wiki, but
)
Not exactly the Wiki, but it's somewhere in the BOINC Wiki as well... were it not that Trac is down. :-(
Well I started processing
)
Well I started processing these S5R3 Beta WU's to see if there was a speed up in processing time (and consequently an increase in granted credit).
S5R3 Application 4.02 started out at over 66,000 seconds, slowly reduced to a bit over 60,000 seconds. Then a sudden drop to between 52,570 to 50,065 seconds.
Credit started at just 12.02 cr/h rising to 15.96 cr/h (S5R2 gave me 21.4+ cr/h).
I then went to Beta as I was so disappointed with the new S5R3 Wu's.
S5R3 Application 4.09 started well, with the first 3 showing a great drop in processing times
40,307.92 seconds for WU 87374313
40,033.85 seconds for WU 87374374
43,621.74 seconds for WU 87375124
Giving credit of 19.82, 19.96, 18.32 cr/h for each one.
Unfortunately the next one has gone back to the same as the non Beta application with 52,867.22 seconds for WU 87376902
Dropping cr/h back to 15.11.
So S5R2 was giving (slowly dropping over the last few months) 24 cr/h reducing slowly to 21.43 with the last of the S5R2 work units.
S5R3 started giving me 12 and averaged out at 14.4 cr/h, a 32.76% Drop from S5R2.
First 3 Beta WU's gave me an average of 19.34 cr/h a 9.75% Drop from S5R2 but a 25.54% Increase over the first S5R3 WU's.
The last one is back to 29.49% Drop from S5R2 and only a 4.63% Increase over the first S5R3 WU's.
What happened to the speed up?
Forgot to mention that all my S5R3 WU's, including the Beta WU's and the last S5R2 that I did are all of the same 0518.05 frequency (on my AMD Opteron 285 Linux machine).
Hi! Your observations are
)
Hi!
Your observations are consistent with other users' reports:
The variation of runtime in S5R3 is much higher than in S5R2. Hopefully this can be reflected in the future by a more fine grained credits allocation. Variation is routinely 20% and sometimes more.
On average, the new Linux beta app is much faster than the initial stock app, about 20 % on most machines.
Because the variation of runtime is in the same range as the speed-up, it can be expected that the slowest results from the new beta app are about as fast as the fastest results from the old stock app. On average they are still 20 % faster, and I think a 20 % improvement in speed is something of an achievement.
The staff are working on both: further closing the gap between Linux and Windows apps and a better prediction of runtime ==> more accurate credits. Stay tuned.
CU
Bikeman
I just upgraded to the new
)
I just upgraded to the new Kubuntu 7.10 (okay, it's a bit before the release, but who cares- at least my sound works now) on my laptop, since it's working just fine I'm intending to be running Linux as my first OS now. So after running the first 2 WUs with the "normal" app to check that everyting is fine I'll be in for some Linux beta testing.
Yes, I've noticed those variations in runtime aswell. It's a real... let's say annoyance... for beta testing because it's very hard to tell if a new app is really faster or if one just had a shorter WU for the same credit. I'm suffering this problem on my desktop box atm, started using "EAH_NO_GRAPHICS" and it seems to be a little faster, but then, with only 2 WUs crunched after the change, it might still be within normal fluctuation...
I'm not worried about credit, that is going to equal out eventually, anyway (where is the difference between crunching to 50k sec WUs or one 40k and one 60k, in the end it's the same) but it's very hard to judge CPU and app performance if there is so much fluctuaction in the runtime/credit ratio. One has to collect quite a lot of examples before being able to say sth halfway definite.
RE: Hi! Your observations
)
Hello Bikeman,
I have not noticed that Windows S5R3 is faster than S5R2 as my credit has dropped from a bit over 16 to about 14 now (AMD 4800+ Win XP). All it shows is that there has not been as big a drop as in the Linux application.