We are testing the new applications for Windows and Linux. They should be out tomorrow.

The are very many added features from the science point of view. From a practical point of view the multiplier will pass from 1.5x to 2.0x for everybody (SETI 2.4x). We will give further 25% for results returned within two days.
Speed should be the same.

gdf

The applications are ready and tested.
We are waiting tomorrow, as today we are submitting several updated WUs.
If we change two things, we would not know what's wrong in case of problems.

Best, gdf

I assume that the new apps will d/l automatically?

I assume that the new apps will d/l automatically?

Yes, they will ... I already have two 6.63 tasks on my queue ... I should be starting them in about 4-6 hours ... I hope they don't error out

I assume that the new apps will d/l automatically?

Yes, they will ... I already have two 6.63 tasks on my queue ... I should be starting them in about 4-6 hours ... I hope they don't error out

I managed to complete my first 6.63 task here. The timestep is quite high though. I might try the new Boinc version and see how it copes.

Rob

I completed my first and the T/S was about the same ... the run time slightly higher.

The 4 in work should start pumping out in the next couple hours, the next in line looks to be 8:12 which is about 2 hours longer than before. So, I will have to look to see what is up with that if it is an outlier or just a longer running task ...

More to come I am sure ...

We are testing the new applications for Windows and Linux. They should be out tomorrow....

is this related with NO WORK available for PS3 ?


good job guys ;)

We are testing the new applications for Windows and Linux. They should be out tomorrow....

is this related with NO WORK available for PS3 ?


good job guys ;)

ATM, I see plenty of PS3 work and No GPU work..........

---

mike

We have performed a further application update to fix one bug which did not allow us to run the new type of workunits.

gdf

We have performed a further application update to fix one bug which did not allow us to run the new type of workunits.

gdf

So we should start to see 6.64 tasks soon?

We have performed a further application update to fix one bug which did not allow us to run the new type of workunits.

gdf

So we should start to see 6.64 tasks soon?

It says the application (note: hardest page to find!) was applied at 6pm so any prepared after then I guess.

Should I cancel the 6.63 in my queue? Edit: Just did and received a 6.64.

Rob

you don't need to cancel old WUs, these are just fine.
We need the new application for the WUs which we will submit tomorrow.

gdf

We have performed a further application update to fix one bug which did not allow us to run the new type of workunits.

gdf

So it could be very interesting to know, what is this "new type of WUs"... Could you please inform us? :-)

---

From Siberia with love!

It is a rather technical but important change, from now on we will be able to use the Amber force fields, which is more accurate for certain applications.

gdf

It is a rather technical but important change, from now on we will be able to use the Amber force fields, which is more accurate for certain applications.

And all this time I was hoping that we would start using the puce force fields ...

For those mathematically inclined: AMBER force Fields (an acronym for Assisted Model Building and Energy Refinement)...

Details of the new WUs will be posted soon.

gdf

I observe that the 6.64 application runs 4x as long on a seemingly same type of workunit, is that intentional ? It also uses 0.25% CPU time instead of 0.15% with version 6.63. The GPU is much cooler. My impression is that this is not as efficient as before...

I observe that the 6.64 application runs 4x as long on a seemingly same type of workunit, is that intentional ? It also uses 0.25% CPU time instead of 0.15% with version 6.63. The GPU is much cooler. My impression is that this is not as efficient as before...

My first 6.64 started running a little while ago. I am not noticing any difference in elapsed time or GPU temp so far, but I am seeing the CPU utilization going up to 25% from 15%, same as you.

My hardware is a Q6600/GTX280(FOC). Your CPU is faster and our GPUs are similar in speed.

I'm not sure what conclusions to draw from this. I find it very interesting and somewhat perplexing that BOTH of us saw 15% CPU utilization under 6.63 and 25% utilization under 6.64, despite having GPUs that run around the same speed (and hence should require the same amount of servicing by the CPU), yet your CPU is faster.

EDIT:

I just noticed that I have queued up a work unit that looks very different than prior work units. I guess this work unit is one of the new ones just released today. Of note is that the estimated run time is double that of the older tasks.

I suspect what you're seeing is also one of the new ones, and perhaps they're just bigger.

I bet you are also using BOINC version 6.6.20 ? I just read another thread and decided to test it. I got rid of BOINC 6.6.20 and reinstalled 6.4.7 and bingo, I am back to my old high speed crunching !

Yes, I've been using 6.6.20 for a while. It seems to work fine when you only have one GPU, and solves some problems I had with 6.4.7, most notably the failure to keep all CPU cores busy.

P.S. Check the edit I made to my previous post.