I have lost the bubble here. Are we still in a test phase with the optimized apps or are we doing science with them? Just curious.

Jim

I think it is sort of like test-science. Even the tests were supposed to be doing searches if they worked.

The project is supposed to be doing searches, but seems to me the focus isn't on the milkyway part so much as the computer distribution and "fairness".

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Actually, right now we're comparing the numbers coming in with our asynchronous newton method to what we've done (very slowly) using a synchronous newton method and gradient descent on our cluster. When the current newton method searches (and one more version i'm working on) are working smoothly they should give us more accurate numbers for the current stripes we're computing on (79, 82 and 86) than we have previously had, because what cluster version was using a very inaccurate integral and likelihood calculation.

So yes, in addition to figuring out how to do these accurate local optimization methods asynchronously on BOINC (which is also science), we're doing some real astronomy in getting the most accurate 3-dimensional model of the milkyway galaxy there is (or at least pieces of it).

Once we have the search working correctly, we'll be starting up a whole slew of other strips of the galaxy. I think there's a couple hundred of them that need to be crunched.

After that... there's the problem of putting them all together :D

---

So currently I am seeing a 20x improvement in my crunch times. Is that due to the optimized app, shorter WUs or both?

Thanks,
Jim

Optimised app. The WUs are different too, but I don't know about shorter.

Unless you are talking about the difference from the 10 hour ones to the current?

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Yes. Instead of ten hours, I am seeing 30 minutes or less.

Jim

So currently I am seeing a 20x improvement in my crunch times. Is that due to the optimized app, shorter WUs or both?

Thanks,
Jim

Keeping in mind that, yes, the old and new apps are processing the workunits differently:

Old App (1.22): ~24h38m (DCF around 48.xxx-49.xxx)
Milksop app (v3): ~0h28m (DCF around 0.93x)

New app (0.7): ~2h50m-3h2m (DCF 0.17x-.19x)

And this is for a two year old Dell Laptop (Intel 1.4GHz Celeron M, MMX SSE SSE2)


[edit]Typo[/edit]

---

Optimised app. The WUs are different too, but I don't know about shorter.

The improvement of the new app is larger than what one sees from the shorter crunch times. One should keep in mind that the new WUs are in fact approximately four times as "long" as the old ones. That means they are doing roughly 4 times the work of the old 270 credit WUs.

Impressive!