i could be wrong but it think some of you might missunderstanding aksof on this (or i am :) ). This mostly all just testing some diffrent use of SSE and the patcher system ect. As i understand this we're beta testing ideas here not a new optimised app but working towards "building a stable one".
Correct me if i'm wrong please akosf. Just worried some might take this wrong (or i am) and start sticking it on their machines as an optimized app not as a beta that needs an eye kept on.
i could be wrong but it think some of you might missunderstanding aksof on this (or i am :) ). This mostly all just testing some diffrent use of SSE and the patcher system ect. As i understand this we're beta testing ideas here not a new optimised app but working towards "building a stable one".
Correct me if i'm wrong please akosf. Just worried some might take this wrong (or i am) and start sticking it on their machines as an optimized app not as a beta that needs an eye kept on.
It's a test of some low level optimization for:
1. eliminated double jumps (hot loop size: 4901)
2. reduced amount of FPU macro ops (4831)
3. removed double loads on general purpose registers (4675)
4. reoptimized SSE part (4569)
And yes its a beta test. What's your point ?
Its a public board, so anyone can patch the app. him/herself.
Don't mess it up like on S@H... they can test their cr*p at the beta forum.
I think there was no offense intended by Pepperammi. He just wanted to make sure that everyone using the patches knows that they're beta/alpha versions, which is a good point (in case someone missed it before).
1. eliminated double jumps (hot loop size: 4901)
2. reduced amount of FPU macro ops (4831)
3. removed double loads on general purpose registers (4675)
4. reoptimized SSE part (4569)
And yes its a beta test. What's your point ?
Its a public board, so anyone can patch the app. him/herself.
Don't mess it up like on S@H... they can test their cr*p at the beta forum.
NO! don't want that hell over on Seti coming here. good to see you around here by the way :)
I just got the feeling that it was maybe starting to be looked at like a new optimized app when it's still early beta. I'm glad a lot of people are joining and helping out. More machines means we get makes it even more stable across many platforms.
Hope my small contributions help.
Definatly no offense meant. Freindly reminder to any who get the wrong idea at most but welcome anyone who wants to help too.
i could be wrong but it think some of you might missunderstanding aksof on this (or i am :) ). This mostly all just testing some diffrent use of SSE and the patcher system ect. As i understand this we're beta testing ideas here not a new optimised app but working towards "building a stable one".
Correct me if i'm wrong please akosf. Just worried some might take this wrong (or i am) and start sticking it on their machines as an optimized app not as a beta that needs an eye kept on.
You're right.
Anyway better to remind that again.
This way, no surprise and later (i guess) it will be possible to open a thread with a stable version for all people.
Just started a new (long) S5 WU with Patch 0004 on an Athlon XP 1700+ (which is *NOT* SSE3 capable)
Let's compare the times....
h1_0804.0_S5R1__700_S5R1a with the official app took 51528 sec
h1_0804.0_S5R1__693_S5R1a with Patch 0004 applied:
3,5% finished in 28:46 min (=1726 sec) will need 49315 sec for 100%
7,0% finished in 56:44 min (=3404 sec) will need 48628 sec for 100%
that's nearly 3000 sec (or 6%) less... which would reduce the 'total needed time' by 22 days...
...but now it is late enough in germany... I will go to bed...
Thanks to keep your feelings about Seti@home far away from this forum.
Oh jesus no what have i started.
please everyone i'm sorry for it all. No ill meaning or intent meant. please don't take me seriously. If it'll help, moderators please delete my last posts on the issue. I dont want things to go bad. I personally fully understand crunch3rs concerns and also hope einstien stays the way it alway has been, a great project to be a part of :-) I maybe worded that initial post a little to seriously so sorry to all.
now
@aksof only a hour or so from getting the first result back with your first 'S5T0000' version. Was swaped over to yours at about 50% and a 2nds a few hours away with same version from start.
Got S5T0001 on second machine and all seems well. I'll let them work their way through. Thanks again for all your time and to crunch3r for helping with links.
Just a though. Some time off yet but maybe one day.
I know Bruce and all the others (sorry rubish with names) incorporated cpudetection to find cpu abilities and send out the best app. Maybe eventually any optimized apps will be allowed to be part of that system? Think the current official app goes to SSE maybe SSE2 and whatever maybe created here could be sent to SSE3 machines as part of the system?
i could be wrong but it think
)
i could be wrong but it think some of you might missunderstanding aksof on this (or i am :) ). This mostly all just testing some diffrent use of SSE and the patcher system ect. As i understand this we're beta testing ideas here not a new optimised app but working towards "building a stable one".
Correct me if i'm wrong please akosf. Just worried some might take this wrong (or i am) and start sticking it on their machines as an optimized app not as a beta that needs an eye kept on.
RE: i could be wrong but it
)
It's a test of some low level optimization for:
1. eliminated double jumps (hot loop size: 4901)
2. reduced amount of FPU macro ops (4831)
3. removed double loads on general purpose registers (4675)
4. reoptimized SSE part (4569)
And yes its a beta test. What's your point ?
Its a public board, so anyone can patch the app. him/herself.
Don't mess it up like on S@H... they can test their cr*p at the beta forum.
I think there was no offense
)
I think there was no offense intended by Pepperammi. He just wanted to make sure that everyone using the patches knows that they're beta/alpha versions, which is a good point (in case someone missed it before).
MrS
Scanning for our furry friends since Jan 2002
RE: It's a test of some low
)
NO! don't want that hell over on Seti coming here. good to see you around here by the way :)
I just got the feeling that it was maybe starting to be looked at like a new optimized app when it's still early beta. I'm glad a lot of people are joining and helping out. More machines means we get makes it even more stable across many platforms.
Hope my small contributions help.
Definatly no offense meant. Freindly reminder to any who get the wrong idea at most but welcome anyone who wants to help too.
RE: i could be wrong but it
)
You're right.
Anyway better to remind that again.
This way, no surprise and later (i guess) it will be possible to open a thread with a stable version for all people.
[
@ Crunch3r Thanks to keep
)
@ Crunch3r
Thanks to keep your feelings about Seti@home far away from this forum.
[
Just started a new (long) S5
)
Just started a new (long) S5 WU with Patch 0004 on an Athlon XP 1700+ (which is *NOT* SSE3 capable)
Let's compare the times....
h1_0804.0_S5R1__700_S5R1a with the official app took 51528 sec
h1_0804.0_S5R1__693_S5R1a with Patch 0004 applied:
3,5% finished in 28:46 min (=1726 sec) will need 49315 sec for 100%
7,0% finished in 56:44 min (=3404 sec) will need 48628 sec for 100%
that's nearly 3000 sec (or 6%) less... which would reduce the 'total needed time' by 22 days...
...but now it is late enough in germany... I will go to bed...
Udo
RE: Thanks to keep your
)
Oh jesus no what have i started.
please everyone i'm sorry for it all. No ill meaning or intent meant. please don't take me seriously. If it'll help, moderators please delete my last posts on the issue. I dont want things to go bad. I personally fully understand crunch3rs concerns and also hope einstien stays the way it alway has been, a great project to be a part of :-) I maybe worded that initial post a little to seriously so sorry to all.
now
@aksof only a hour or so from getting the first result back with your first 'S5T0000' version. Was swaped over to yours at about 50% and a 2nds a few hours away with same version from start.
Got S5T0001 on second machine and all seems well. I'll let them work their way through. Thanks again for all your time and to crunch3r for helping with links.
Just a though. Some time off
)
Just a though. Some time off yet but maybe one day.
I know Bruce and all the others (sorry rubish with names) incorporated cpudetection to find cpu abilities and send out the best app. Maybe eventually any optimized apps will be allowed to be part of that system? Think the current official app goes to SSE maybe SSE2 and whatever maybe created here could be sent to SSE3 machines as part of the system?
Patched an Athlon 64 SSE2
)
Patched an Athlon 64 SSE2 (and not SSE3)
It's late here so... see you tomorrow.
[