Let me know if the recompiles of 0.9 are running as fast as they used to. Thanks!

---

Are any of these apps being tested first or being put out and let the public test them? Shouldn't these new apps be put out as "test apps" so that adds another level of testing after your tests are done to check that the app works before they are made the current official app?

I think too many apps are being thrown out too quickly in the last week, and it is only causing confusing for some people. Along with the many errors that have occured only cause more havoc.

---

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

Are any of these apps being tested first or being put out and let the public test them? Shouldn't these new apps be put out as "test apps" so that adds another level of testing after your tests are done to check that the app works before they are made the current official app?

I think too many apps are being thrown out too quickly in the last week, and it is only causing confusing for some people. Along with the many errors that have occured only cause more havoc.

We could do that, but the only problem is when we were running two seperate apps (one regular and one test), the server really suffered from bad performance. I think from here on out most changes to the application will be in the form of different compiler flags and small changes in the code for optimization so I don't see this as a huge issue.

When we move to beta (remember this project is STILL alpha), I think then we'll get another server that's either fast enough to handle running a test app and regular app or have two seperate machines, one running test apps and the other doing the regular MW stuff.

---

If you limit the # of test wu's to one or two hundred then it shouldn't add much strain at all but still give results to show if the test app worked or not.

---

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

If you limit the # of test wu's to one or two hundred then it shouldn't add much strain at all but still give results to show if the test app worked or not.

We can give it a shot for the next code update and see how the server handles it. If the server can handle it it's probably a good practice to get into the habit of anyways.

---

64-bit Linux validates ok but takes double time to complete compared with 32-bit

Let me know if the recompiles of 0.9 are running as fast as they used to. Thanks!

Working the same as v0.07 did.
The DCF is 0.12

0.10 4 Linux x86_64 takes 4200 s, 0.10 4 Lin. i686 takes 1800 s on same PC.

0.07 8400 sec., 0.10 8200 sec. on Linux x86_64 Intel D940.

OS X still takes about twice as long on Intel Mac as it did before.

I found that v0.09 took more than twice as long as 0.07. v0.10 is possibly faster than 0.09 but still a lot slower than 0.07.

---

Proud member of BOINC@AUSTRALIA

Was crunching work units in just over an hour, but for the last 2 days they have been taking twice as long to complete.

---

OS X still takes about twice as long on Intel Mac as it did before.

Then it must depend which Intel Mac you have. 0.7, 0.8, 0.9 and 0.10 have all been pretty much the same speed for me.

32-bit Linux is one or two minutes faster than before.
64-bit Linux takes double time.

Same for me
0.10
Linux 64 bits still around 1h30 instead of 42 minutes 0.07

62698794 62752634 19 Jan 2009 8:41:38 UTC 19 Jan 2009 11:11:42 UTC Over Success Done 5,307.89 41.77 39.84
62682174 62736354 19 Jan 2009 7:29:18 UTC 19 Jan 2009 10:19:08 UTC Over Success Done 5,533.33 43.54 41.09
62675156 62729576 19 Jan 2009 7:00:09 UTC 19 Jan 2009 8:41:38 UTC Over Success Done 5,390.89 42.42 39.84

---

OS X still takes about twice as long on Intel Mac as it did before.

Then it must depend which Intel Mac you have. 0.7, 0.8, 0.9 and 0.10 have all been pretty much the same speed for me.

I have two core duo mini's runing Tiger and one core 2 duo MacBook running Leopard. What are you running?

Just checking on v .10 on my windows machines looks like completion time has increased 50% over v .07. Completion times have gone from 2000 secs to 3000 secs.

I have seen very little increase or decrease from v. 0.7 on either my Mac or PC.

Jim

No change between version 0.1 and 0.07 on windows 32 bits
core duo T7250 2GHz

around 1 hour and 10 minutes.

There is definitely something wrong with the OS X version for Intel.

I have four computers doing MW:

333MHz iMac PPC G3 OS X 10.3.9 ~30500 cpusec/WU
1.33GHz iBook PPC G4 OS X 10.5.6 ~ 9100 cpusec/WU 4 times faster clock, 30% of the imac time, altivec helps a bit
1.67GHz MacBookPro Core Duo OS X 10.4.11 ~ 8100 cpusec/wu 5 times faster clock, 25% of the imac time; I would expect around 6100 cpusec, based on clock speed alone. If I remember correctly, it used to actually take in the low 4000's, because of SSE2 and others(?)
2.4GHz MacBookPro Core 2 Duo OS X 10.4.11 ~ 7200 cpusec/wu 7.2 times faster clock, 23% of the imac time; I would expect around 4200 cpusec based on clock speed alone. I think it used to take around 3600.

My conclusion is there is definitely something lacking in the Intel Mac compilation.

C

---

Team MacNN