I only registered on your site because you had a nicer stats sig than boincstats. I could care less about teams.
Looks like you gouys are being "head-hunted", and I thought that only happened in the buisness world!
There are 10^11 stars in the galaxy. That used to be a huge number. But it's only a hundred billion. It's less than the national deficit! We used to call them astronomical numbers. Now we should call them economical numbers. - Richard Feynman
I only registered on your site because you had a nicer stats sig than boincstats. I could care less about teams.
Looks like you gouys are being "head-hunted", and I thought that only happened in the buisness world!
Something like that. :)
I've got friends crunching that I'd team with if we were in the same project, but they're all doing seti and there aren't any cross project teaming options afaik.
Will pop back for the next one, unless it's been optimised as much as it can.
Can you do anyone more or is that it???
He's working on an SSE3/3Dnow parallel execution app. Dunno how far along it is, but we're looking at upto a 2x gain. Unless he tests other tricks in it as well, I'm sure it'll be less but at least for those of us with newer cpus it'll be sweet.
Successful hosts: 565377 with client S40, 545482 with original client.
Errors: 485312 with S40.12, 514055 with S40.12
Both machines with errors are A64 X2s. For mine (514055) it's the first error since... well, I can't remember having an albert error before. For the second machine I can say at least that this WU is the only failed one within the last 300 WUs (which are in the database).
Both hosts give basically the same stderr_out:
***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x0040AA13 read attempt to address 0x01002458
***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x0040AA13 read attempt to address 0x01002458
There are a look-up table reading, that is based on a dirty stack usage.
Probably the new codes (41.xx) don't have this problem, because they use statical look-up tables.
I only registered on your
)
I only registered on your site because you had a nicer stats sig than boincstats. I could care less about teams.
RE: I only registered on
)
Looks like you gouys are being "head-hunted", and I thought that only happened in the buisness world!
There are 10^11 stars in the galaxy. That used to be a huge number. But it's only a hundred billion. It's less than the national deficit! We used to call them astronomical numbers. Now we should call them economical numbers. - Richard Feynman
RE: RE: I only registered
)
Something like that. :)
I've got friends crunching that I'd team with if we were in the same project, but they're all doing seti and there aren't any cross project teaming options afaik.
RE: I only registered on
)
Likewise.
New app from Akosf so I
)
New app from Akosf so I thought I'd try a few WUs out, despite dropping Einstein to focus on others........
Nice work mate.......some WUs are running sub-1 hour on my XP2800+ at stock speed.
Fantastic.......
Will pop back for the next one, unless it's been optimised as much as it can.
Can you do anyone more or is that it???
RE: Will pop back for the
)
He's working on an SSE3/3Dnow parallel execution app. Dunno how far along it is, but we're looking at upto a 2x gain. Unless he tests other tricks in it as well, I'm sure it'll be less but at least for those of us with newer cpus it'll be sweet.
Running two nearly identical
)
Running two nearly identical dual xeon systems here, both are overclocked to 2.8GHz/800FSB, running S40.12
Hyperthreading disabled:
20-25 minutes for short
75-80 minutes for long
Hyperthreading enabled:
40-45 minutes for short
145-155 minutes for long
I think I have a bug with
)
I think I have a bug with S40.12 here!
WU: http://einsteinathome.org/workunit/7492465
Successful hosts: 565377 with client S40, 545482 with original client.
Errors: 485312 with S40.12, 514055 with S40.12
Both machines with errors are A64 X2s. For mine (514055) it's the first error since... well, I can't remember having an albert error before. For the second machine I can say at least that this WU is the only failed one within the last 300 WUs (which are in the database).
Both hosts give basically the same stderr_out:
***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x0040AA13 read attempt to address 0x01002458
1: 05/01/06 14:32:30
1: e:\\einsteinathome\\cfs\\windows_build\\albert4.37\\cfslaldemod.c(928) +4 bytes (TestLALDemod)
1: SymGetLineFromAddr(): GetLastError = 126
Hope this helps akosf.
Regards, MrS
Scanning for our furry friends since Jan 2002
RE: ***UNHANDLED
)
There are a look-up table reading, that is based on a dirty stack usage.
Probably the new codes (41.xx) don't have this problem, because they use statical look-up tables.
Thx. Nice to know that it's
)
Thx. Nice to know that it's already fixed :)
MrS
Scanning for our furry friends since Jan 2002