15% slower on Linux, core2duo
2% slower on Windows, Core2quad (Tjeerd's comp)
Other R3 results on Linux, this is the current Top2 on E@H, dual Xeon 5355, http://einsteinathome.org/host/795801,
how many percent slow down is this!
R3:
45,030.65 - 220.28
43,890.32 - 220.28
46,109.52 - 220.28
R2:
102,579.78 - 650.90
103,871.38 - 650.90
100,483.97 - 650.98
Looking bad for the penguins this run, like they dont have enough problems already with the polar caps melting and everything!
th3: *lol* nice way to put it. The little devil/daemon gets a whacking too, as I read in the "S5R3"-thread... maybe an angel being a bit overly motivated...
Anyway, I'm having another penguin crunch right now (might be a guinea pig, really) to see if I can confirm the slowdown on my box.
The absolute numbers appear kind of slow, I guess this is with HyperThreading?
CU
Bikeman
yes, it's with hyperthreading!
Interesting.
Question to Bernd: is it possible that the new app are kind of less hyperthreading-friendly, because they are heavier on the FPU and have less integer stuff to mix with the floating point stuff? E.g. more FStat and less pattern matching, as a consequence to of the fewer sky grid points? Could also help to explain the compiler specific differences in performance.
The absolute numbers appear kind of slow, I guess this is with HyperThreading?
CU
Bikeman
yes, it's with hyperthreading!
Interesting.
Question to Bernd: is it possible that the new app are kind of less hyperthreading-friendly, because they are heavier on the FPU and have less integer stuff to mix with the floating point stuff? E.g. more FStat and less pattern matching, as a consequence to of the fewer sky grid points? Could also help to explain the compiler specific differences in performance.
So The score so far: 15%
)
So The score so far:
15% slower on Linux, core2duo
2% slower on Windows, Core2quad (Tjeerd's comp)
Other R3 results on Linux, this is the current Top2 on E@H, dual Xeon 5355,
http://einsteinathome.org/host/795801,
how many percent slow down is this!
R3:
45,030.65 - 220.28
43,890.32 - 220.28
46,109.52 - 220.28
R2:
102,579.78 - 650.90
103,871.38 - 650.90
100,483.97 - 650.98
Looking bad for the penguins this run, like they dont have enough problems already with the polar caps melting and everything!
Team Philippines
My first S5R3 finished and
)
My first S5R3 finished and validated ok:
h1_0541.80_S5R2__27_S5R2c in 299,025.58 Sec. with 653.29 credits - 457,72 sec/credit
h1_0541.80_S5R2__182_S5R3a in 119,813.22 Sec. with 220.28 credits - 543,91 sec/credit
Udo
Got my first 4 yesterday,
)
Got my first 4 yesterday, I'll let you know.
th3: *lol* nice way to put
)
th3: *lol* nice way to put it. The little devil/daemon gets a whacking too, as I read in the "S5R3"-thread... maybe an angel being a bit overly motivated...
Anyway, I'm having another penguin crunch right now (might be a guinea pig, really) to see if I can confirm the slowdown on my box.
First one finished in 11hr
)
First one finished in 11hr 14min :)
e6600 quad @ 2.5ghz
2418 floating point
5227 integer
e6750 dual @ 3.71ghz
3657 floating point
8105 integer
RE: My first S5R3 finished
)
The absolute numbers appear kind of slow, I guess this is with HyperThreading?
CU
Bikeman
RE: RE: My first S5R3
)
yes, it's with hyperthreading!
Udo
RE: RE: RE: My first
)
Interesting.
Question to Bernd: is it possible that the new app are kind of less hyperthreading-friendly, because they are heavier on the FPU and have less integer stuff to mix with the floating point stuff? E.g. more FStat and less pattern matching, as a consequence to of the fewer sky grid points? Could also help to explain the compiler specific differences in performance.
CU
H-B
RE: RE: RE: RE: My
)
I recently received a
)
I recently received a boatload of S5R3 WUs on my Intel Q6600 (overclocked to 3.4G) and running XP Pro. I have run a few for a comparison.
The S5R3 WUs take about 7.5 hours for 219 credits.
The S5R2 WUs took about 23 hours for 638 credits.
There seems to be no great difference on my system.
Eeyore