Significant app optimization is on hold while the team trys to find the last handful of low occurence bugs.
Hmmm, hard to believe. Windows version 4.13 brought a 20% performance increase over version 4.07: http://einsteinathome.org/task/87874714 . They obviously DO work on optimizations for Windows.
So, did you mean "Significant app optimization for Mac PPC is on hold ..."?
I'm not certain what you're trying to tell me by linking to a single WU, but there's been no mention of a speedup either by bernd in the 4.13 thread, nor by any of the people replying to it. It's possible that somethin was done to result in a speadup, but if so it wasn't done intentionally.
the current results on my two machines are 50-62k vs 59-64, and 49-62 vs 60-76. In the first case the peak to valley spreads from the combined range are within the ranges seen from people charting runtime stats long enough to get the entire curve (28% vs 21% and 34% in the graph I found). The 55% spread in my second machine is somewhat larger, but I also use it much more heavily. Gaming sessions that max one core will badly slow the two einsein proceses down by forcing them to fight over cache resources. I've seen 33% increases in the amount of CPU time needed in earlier runs, so while somewhat suggestive the numbers from my second box aren't conclusive.
Windows version 4.13 brought a 20% performance increase over version 4.07:
I agree that Windows 4.13 and 4.15 are substantially faster than 4.07, though on my Core 2 machines the difference is about 10%, definitely not 20%. I posted evidence I think pretty strong on that point here.
However, based on the introductory comment Bernd made for the 4.11 beta, I think the improvement was not a change to the primary science code, but rather to error-handling and containment.
My scan did not pick up enough 4.11 results to give an effective comparison for that specific release.
Significant app optimization is on hold while the team trys to find the last handful of low occurence bugs.
Hmmm, hard to believe. Windows version 4.13 brought a 20% performance increase over version 4.07: http://einsteinathome.org/task/87874714 . They obviously DO work on optimizations for Windows.
So, did you mean "Significant app optimization for Mac PPC is on hold ..."?
Most of the speedup we see in the Windows app now is the result of replacing debug code that introduced a slowdown earlier. The next PPC app will surely include these changes.
I'm not certain what you're trying to tell me by linking to a single WU, but there's been no mention of a speedup either by bernd in the 4.13 thread, nor by any of the people replying to it. It's possible that somethin was done to result in a speadup, but if so it wasn't done intentionally.
Dan,
sorry, it was meant to be the link to the computer: http://einsteinathome.org/host/624455/tasks . There you can see that the speed-up is in fact 20% (67,575 seconds for 233.81 credit versus 84,203 seconds for 218.52 credits)
Most of the speedup we see in the Windows app now is the result of replacing debug code that introduced a slowdown earlier. The next PPC app will surely include these changes.
That doesn't appear to be listed in the mini changelogs that came with any of the beta apps. Had it been I probably would've swtiched over instead of waiting for 4.13 to become hte official app.
Most of the speedup we see in the Windows app now is the result of replacing debug code that introduced a slowdown earlier. The next PPC app will surely include these changes.
That doesn't appear to be listed in the mini changelogs that came with any of the beta apps. Had it been I probably would've swtiched over instead of waiting for 4.13 to become hte official app.
Dan,
4.13 IS the official version for more than a week now. Please do not pretend to know about future releases ("Significant app optimization is on hold while the team trys to find the last handful of low occurence bugs. ") without even using the current versions.
Most of the speedup we see in the Windows app now is the result of replacing debug code that introduced a slowdown earlier. The next PPC app will surely include these changes.
That doesn't appear to be listed in the mini changelogs that came with any of the beta apps. Had it been I probably would've swtiched over instead of waiting for 4.13 to become hte official app.
Dan,
4.13 IS the official version for more than a week now. Please do not pretend to know about future releases ("Significant app optimization is on hold while the team trys to find the last handful of low occurence bugs. ") without even using the current versions.
You're reading something other than what I was trying to say. What I meant was that if the changelog would've mentioned the speedup from removing unneeded debugging code I would have switched 2 or 3 days earlier, and flushed my queue (3 days) to bring the new app into play sooner. Since the official thread mentioned nothing about performance gains I assumed it would run about the same and waited for an offial rollout.
The debug code wasn't so much removed but changed so that it is more useful (and happens to be faster). The focus of the Win beta tests are still on stability, I guess that's why the changelists don't dwell on performance so much.
The debug code wasn't so much removed but changed so that it is more useful (and happens to be faster). The focus of the Win beta tests are still on stability, I guess that's why the changelists don't dwell on performance so much.
Do you know if there has been more progress on finding out the wide variations in runtime?
RE: Significant app
)
Hmmm, hard to believe. Windows version 4.13 brought a 20% performance increase over version 4.07: http://einsteinathome.org/task/87874714 . They obviously DO work on optimizations for Windows.
So, did you mean "Significant app optimization for Mac PPC is on hold ..."?
I'm not certain what you're
)
I'm not certain what you're trying to tell me by linking to a single WU, but there's been no mention of a speedup either by bernd in the 4.13 thread, nor by any of the people replying to it. It's possible that somethin was done to result in a speadup, but if so it wasn't done intentionally.
the current results on my two machines are 50-62k vs 59-64, and 49-62 vs 60-76. In the first case the peak to valley spreads from the combined range are within the ranges seen from people charting runtime stats long enough to get the entire curve (28% vs 21% and 34% in the graph I found). The 55% spread in my second machine is somewhat larger, but I also use it much more heavily. Gaming sessions that max one core will badly slow the two einsein proceses down by forcing them to fight over cache resources. I've seen 33% increases in the amount of CPU time needed in earlier runs, so while somewhat suggestive the numbers from my second box aren't conclusive.
RE: Windows version 4.13
)
I agree that Windows 4.13 and 4.15 are substantially faster than 4.07, though on my Core 2 machines the difference is about 10%, definitely not 20%. I posted evidence I think pretty strong on that point here.
However, based on the introductory comment Bernd made for the 4.11 beta, I think the improvement was not a change to the primary science code, but rather to error-handling and containment.
My scan did not pick up enough 4.11 results to give an effective comparison for that specific release.
RE: RE: Significant app
)
Most of the speedup we see in the Windows app now is the result of replacing debug code that introduced a slowdown earlier. The next PPC app will surely include these changes.
CU
Bikeman
RE: I'm not certain what
)
Dan,
sorry, it was meant to be the link to the computer: http://einsteinathome.org/host/624455/tasks . There you can see that the speed-up is in fact 20% (67,575 seconds for 233.81 credit versus 84,203 seconds for 218.52 credits)
RE: Most of the speedup we
)
That doesn't appear to be listed in the mini changelogs that came with any of the beta apps. Had it been I probably would've swtiched over instead of waiting for 4.13 to become hte official app.
RE: RE: Most of the
)
Dan,
4.13 IS the official version for more than a week now. Please do not pretend to know about future releases ("Significant app optimization is on hold while the team trys to find the last handful of low occurence bugs. ") without even using the current versions.
RE: RE: RE: Most of
)
You're reading something other than what I was trying to say. What I meant was that if the changelog would've mentioned the speedup from removing unneeded debugging code I would have switched 2 or 3 days earlier, and flushed my queue (3 days) to bring the new app into play sooner. Since the official thread mentioned nothing about performance gains I assumed it would run about the same and waited for an offial rollout.
Hi! The debug code wasn't
)
Hi!
The debug code wasn't so much removed but changed so that it is more useful (and happens to be faster). The focus of the Win beta tests are still on stability, I guess that's why the changelists don't dwell on performance so much.
CU
Bikeman
RE: The debug code wasn't
)
Do you know if there has been more progress on finding out the wide variations in runtime?