Thanks for the heads-up about AMDs having problems under Windows, I'll draw my conclusions from that. Don't worry, you're not going to lose crunching time- thank goodness I dual boot!
Thanks for the heads-up about AMDs having problems under Windows, I'll draw my conclusions from that. Don't worry, you're not going to lose crunching time- thank goodness I dual boot!
Yeah! Good for the project, good for you and good for our team. :-)
You should try to contact with Bernd Machenschalk to find the cause of this fault. I think your OS cause it, but i'm not sure.
akosf
Akos,
I'm not the owner of that host. I don't have an S5R2 problem, because I stopped doing work for this project when S5R1 ran out. :-( With my background in software development, what was being said about R2 prior to its' release was enough for me to recognize that it should not be in production.
Since I have an AMD, and an overclocked one at that (so in theory more vulnerable to whatever problems there may be), I'll try out 1 or 2 S5R2 units. Perhaps they will help.
You should try to contact with Bernd Machenschalk to find the cause of this fault. I think your OS cause it, but i'm not sure.
akosf
Akos,
I'm not the owner of that host. I don't have an S5R2 problem, because I stopped doing work for this project when S5R1 ran out. :-( With my background in software development, what was being said about R2 prior to its' release was enough for me to recognize that it should not be in production.
Since I have an AMD, and an overclocked one at that (so in theory more vulnerable to whatever problems there may be), I'll try out 1 or 2 S5R2 units. Perhaps they will help.
Brian
@ Akos: This is my first unit of S5R2. I was suggesting that you attempt to contact the owner of the other host (which is not me) that was having all the errors. They list their country as Spain, and have no way for me to contact them (no web site listed, no email listed in profile, etc...). My thought was that you or someone involved with the project could pull the email record for the account and send them an email asking if they would work with you on figuring out what was wrong. I doubt it is the OS. S5RI was working fine for them. S5R2 has been crashing constantly.
At any rate, the initial estimate on an overclocked AMD Athlon64 3700+ (San Diego) @ 2.75GHz is 20h 17m. No crash of the unit so far. One thought here is that the other host listed above is using an Athlon64 3200+. One thing that was improved in the San Diego core Athlon64 that is not present in the Newcastle (130mm) and Winchester (90mm) cores is the K8 Integrated Memory Controller. The Venice and San Diego cores had improvements in the memory controller. Another difference between the older processors and the Venice/San Diego cores is SSE3 support, so that might be something to consider as well.
acording to earlier posts by either Bruce or Bernd there's roughly a 4x spread in WU size in s5r2. At present there doesn't seem to be any control over what hosts recieve what WUs, given the frantic nature of getting this app out before s5ri completed I'd imagine a WU/cruncher partition like with s5r1's slowere hosts only getting small WUs is on the TBD list but hasn't been implemented yet.
acording to earlier posts by either Bruce or Bernd there's roughly a 4x spread in WU size in s5r2. At present there doesn't seem to be any control over what hosts recieve what WUs, given the frantic nature of getting this app out before s5ri completed I'd imagine a WU/cruncher partition like with s5r1's slowere hosts only getting small WUs is on the TBD list but hasn't been implemented yet.
The Athlon64 3200+ is not a "slower host". Sure, it's slower than mine and mine is slower than a Core 2. However, whoever that is in Spain has a "fast host" because every result is crashing :-(
Edit: Oh yeah, the crashes have driven their WU quota to only 4/day
And in VMWare, too. One would think that costs a few flops extra. Really impressive, good reason to run my Debian more over the next time- and tip off my mate who runs all those AMD hosts...
Hi Brian, RE: Hello
)
Hi Brian,
You should try to contact with Bernd Machenschalk to find the cause of this fault. I think your OS cause it, but i'm not sure.
akosf
Thanks for the heads-up about
)
Thanks for the heads-up about AMDs having problems under Windows, I'll draw my conclusions from that. Don't worry, you're not going to lose crunching time- thank goodness I dual boot!
RE: Thanks for the heads-up
)
Yeah! Good for the project, good for you and good for our team. :-)
cu,
Michael
RE: Hi Brian, RE: Hello
)
Akos,
I'm not the owner of that host. I don't have an S5R2 problem, because I stopped doing work for this project when S5R1 ran out. :-( With my background in software development, what was being said about R2 prior to its' release was enough for me to recognize that it should not be in production.
Since I have an AMD, and an overclocked one at that (so in theory more vulnerable to whatever problems there may be), I'll try out 1 or 2 S5R2 units. Perhaps they will help.
Brian
RE: RE: Hi
)
@ Akos: This is my first unit of S5R2. I was suggesting that you attempt to contact the owner of the other host (which is not me) that was having all the errors. They list their country as Spain, and have no way for me to contact them (no web site listed, no email listed in profile, etc...). My thought was that you or someone involved with the project could pull the email record for the account and send them an email asking if they would work with you on figuring out what was wrong. I doubt it is the OS. S5RI was working fine for them. S5R2 has been crashing constantly.
At any rate, the initial estimate on an overclocked AMD Athlon64 3700+ (San Diego) @ 2.75GHz is 20h 17m. No crash of the unit so far. One thought here is that the other host listed above is using an Athlon64 3200+. One thing that was improved in the San Diego core Athlon64 that is not present in the Newcastle (130mm) and Winchester (90mm) cores is the K8 Integrated Memory Controller. The Venice and San Diego cores had improvements in the memory controller. Another difference between the older processors and the Venice/San Diego cores is SSE3 support, so that might be something to consider as well.
Brian
acording to earlier posts by
)
acording to earlier posts by either Bruce or Bernd there's roughly a 4x spread in WU size in s5r2. At present there doesn't seem to be any control over what hosts recieve what WUs, given the frantic nature of getting this app out before s5ri completed I'd imagine a WU/cruncher partition like with s5r1's slowere hosts only getting small WUs is on the TBD list but hasn't been implemented yet.
RE: acording to earlier
)
The Athlon64 3200+ is not a "slower host". Sure, it's slower than mine and mine is slower than a Core 2. However, whoever that is in Spain has a "fast host" because every result is crashing :-(
Edit: Oh yeah, the crashes have driven their WU quota to only 4/day
This user's Core 2 system
)
This user's Core 2 system running Linux is also crashing
S5R2 errored out
I compared the Windows and
)
I compared the Windows and the Linux app on one host(AMD X2):
Original host OS Win XP Pro:
workunit
63,516.48 sec / 247.51 credits
OpenSuSE 10.2 as guest in VM:
workunit
56,009.63 sec / 337.99 credits
I think there is no further comment about this needed.
cu,
Michael
And in VMWare, too. One would
)
And in VMWare, too. One would think that costs a few flops extra. Really impressive, good reason to run my Debian more over the next time- and tip off my mate who runs all those AMD hosts...