This new version should substantially reduce cpu usage and at the same time work faster under full cpu load provided that you use a new client (6.4.5 for instance). GPU improvement can be substantial for users who fully subscribe CPU with other projects.

GDF.

excellent news. looking forward to getting them once these ones are done.

I'm seeing a CPU usage of 0.00 to 0.02% on a quad, running 4+1. GPU temp is within 1° of the usual value, so speed should be fine. Very nice so far!
Edit: using 6.4.2

MrS

---

Scanning for our furry friends since Jan 2002

This new version should substantially reduce cpu usage and at the same time work faster under full cpu load provided that you use a new client (6.4.5 for instance). GPU improvement can be substantial for users who fully subscribe CPU with other projects.

GDF.

Only for 6.4.5 or also with 6.4.2?

This new version should substantially reduce cpu usage and at the same time work faster under full cpu load provided that you use a new client (6.4.5 for instance). GPU improvement can be substantial for users who fully subscribe CPU with other projects.

GDF.

Only for 6.4.5 or also with 6.4.2?

And for all OS`s? XP/XP64/LIN?

---

Well, it says "windows app" ;)
I assume it should work OK on all windows, but some feedback would be better. (mine was for XP SP2)
And under Linux it was already as well behaved as the win version may be now.

MrS

---

Scanning for our furry friends since Jan 2002

Only for 6.4.5 or also with 6.4.2?

Ascend v6.56 works great with BOINC v6.4.1. Reduced my CPU usage from 13-18% on a quad core Phenom to next to nothing
(90 seconds CPU time out of 120 minutes WU run rime so far).

The new app may be causing a new error, see this thread.

MrS

---

Scanning for our furry friends since Jan 2002

First WU with 6.56 is in at 68.9 ms / 34450 s, without gaming or heavy PC use.

Old ones with the same size (credits) and 6.55, also running 4+1:
72.2 ms / 36140 s
68.3 ms / 34170 s

Wall clock time was 9h 35min = 34500 s - good match!
And CPU usage is down from ~20.000 s to ~1000 s.

MrS

---

Scanning for our furry friends since Jan 2002

We have removed momentarily 6.56 due to errors for several users in order to investigate it.

gdf

Thank You,
I'm back in action with 6.55 :)



Fish

I finished the first two 6.56 WU's, with significantly less cpu usage. No issues yet on my side running BOINC 6.5.0.

The problem with app 6.56 seems to happen only with XP64 OS !

XP SP3, Q6600 3.0GHz, BOINC 6.4.5, GTX260 216sh

2 WUs completed, no problems
increased Approximate elapsed time for entire WU: from 16800s to 18100s
decreases real elapsed time for entire WU: from 19080s to 18000s (not sure)
decreased CPU time: from 9000s to 650s

still working with 3+1

I've still 3 WUs for the application 6.56 in the queue. They working fine on Vista 64 bit. Is it possible, to work further with 6.56 while using a app_info.xml?

---

6.56 worked fine for me. took a bit longer than the 6.55 app that was running at the same time however it used a lot less cpu.

The problem with app 6.56 seems to happen only with XP64 OS !

I agree. Every single report of this error was a machine with either XP-64 (SP1 or 2) or Server 2003. This should help to find the cause, eventually.

MrS

---

Scanning for our furry friends since Jan 2002

Is it possible to leave v6.56 in for 32bit machines?

Every 6.56 WU crashs on my XP 32 box with a 8800GT. Now I have to wait one day to get another WU. The driver is 180.84, BM is 6.5.0.

---

That's strange, you get a variety of different errors. And you're the first with a non-XP64 who got the error 212.
Edit: I just noticed that you already said this in the other thread..

MrS

---

Scanning for our furry friends since Jan 2002