11) Message boards : Graphics cards (GPUs) : Merging of acemd and acemd2 (Message 17337)
Posted 5086 days ago by Profile Paul D. Buck
I don't think it is anything to do with the app_info.xml file: sounds more like BOINC long-term debt, aka 'ATI work fetch priority'.

A subject Richard and others have been trying without much success to get UCB to take seriously ...

There are two other ways to "sometimes" get BOINC back in battery... one is individual project resets to clear the debts and the other is to use the flag in CC Config to clear the debts...

Obviously, if you are going to use the project reset method, wait until you run dry next time and then reset the project and that will reset the debts for that single project ... with multi-project interaction the generalized debt reset is sometimes the only way to get BOINC to behave again ...

Note that in my personal experience you can start seeing the artifacts of the "debt crisis" in as little as a week though most of the time it is tolerable for up to a month ...
12) Message boards : Graphics cards (GPUs) : All completed units are "pending" (Message 17336)
Posted 5086 days ago by Profile Paul D. Buck
Note that now all WUs are on acemd2

So why am I still getting ACEMD? 6.05 as version number...
13) Message boards : Graphics cards (GPUs) : GPUGRID and ATI (Message 17235)
Posted 5089 days ago by Profile Paul D. Buck
It's a bit off topic, but ATI for SETI? I didn't hear about that heard yet. How's performance?

MrS

Still in Beta and it is for the AP tasks only as far as I have been able to find out. Again, the preliminary reports are that it is somewhat like the EaH application in the it uses more CPU than most would like though that is supposedly falling as they have worked the code.

The main coders are on Lunatics and the beta is not a full open beta yet ...
14) Message boards : Graphics cards (GPUs) : I7/gt480 - how to coexist with other projects? (Message 17159)
Posted 5093 days ago by Profile Paul D. Buck
You may have a mis-configuration. Did you set any of the options to max use of CPUs?

Because what you have is not the norm. I have 5 systems and they all run GPU tasks at the same time as the CPUs are busy a bees running tasks from other projects ... to the point where I have, when tasks are available, something like 34 tasks running on my 8 CPUs and 2 GPUs (25 FreeHAL, WUProp, QCN, and 8 from other projects on the CPU and 2 on the 2 GPUs) ...
15) Message boards : Graphics cards (GPUs) : More bad WUs? ------ KASHIF_HIVPR_auto_spawn (Message 17144)
Posted 5093 days ago by Profile Paul D. Buck
skgiven,

BOINC 6.10.51 will randomly stop running tasks on your GPUs, it also has a memory leak... move up to 6.10.56 which has neither of these problems ... don't know if it will cure any of the issues you are having for sure, but it cannot hurt to use the better version ... all the versions between 6.10.45 and 6.10.55 have these two issues at the very least ... I know, I tried most of them ...
16) Message boards : Graphics cards (GPUs) : What's the size of wus? (Message 17121)
Posted 5094 days ago by Profile Paul D. Buck
The last couple beta releases have new network bandwidth controls that may also help you control your situation. I have been running 6.10.56 for several days now and have had no issues (TO THIS POINT)...

They seem to have corrected the issues where one or more of the GPUs would suddenly go idle and a memory leak introduced I don't know when ... the effort is to make sure this version is stable so that it can become the new recommended. I have not seen any posts on the Alpha list (as of yesterday, well this morning, I just checked) about issues ...
17) Message boards : Graphics cards (GPUs) : Fermi (Message 17072)
Posted 5097 days ago by Profile Paul D. Buck
My local Frys had about 6 of them on the shelves as a mix of 470 and 480s ...

Sadly, no 5870 or I might have been tempted to buy another ...
18) Message boards : Graphics cards (GPUs) : Dev BOINC 6.10.55 (Message 17056)
Posted 5097 days ago by Profile Paul D. Buck
It is a minor tweak, in .56, the major change is in 6.10.55 where they commented out the memory size detect code which was causing something bad to happen when called repeatedly ... the more it was called, the sooner it quit returning a value ... no value, BOINC stopped using the GPU ...

When they commented out the code they added a small section to just fill the arrays with fixed values and forgot to set a boolean flag ... anyway, that is the change in .56 that amounts to anything ...

I have been up for more than a day and a half with .55 and now .56 on 4 systems and no lost GPU yet ... so, I think they may have it ... won't say for sure because I was getting random failures of the same ilk with 6.10.45 but it would take a week or more of uptime before you would see it ... so ... 6 more days to go ... :)

Oh, don't forget the memory leak ...
19) Message boards : Graphics cards (GPUs) : Dev BOINC 6.10.55 (Message 17019)
Posted 5098 days ago by Profile Paul D. Buck
All platforms...

Two major changes of significance. There was a memory leak which means that the client grows in size over time and in some cases crashes ... this SEEMS to have been fixed. At least the reports we have so far indicate that there is grow and shrinking going on that is more reasonable ... second the GPU memory test that eventually caused BOINC to stop launching tasks on the GPUs was removed (commented out, it may be restored later) ...

6.10.55 Change Log:

- client: make GPU available RAM measurement #ifdef-selectable,
and default it to off
- client: if we print available GPU RAM (which we now don't)
have a separate timer per GPU type


6.10.54 Change Log:

- client: enable bandwidth quota limit only if both
#MB and #days are nonzero.
- client: fix memory leak
- client: on resume from net bandwidth quota suspend,
apply same random backoff to all transfers.
- client: when changing ncpus via config file,
don't modify host_info.p_ncpus
- client: show effective #CPUs separately from physical #
- client: clear config before rereading config file.
This means that, e.g. if you remove <ncpus>
it will revert to the actual number.
However, it also means that any config params
set via command line will be overridden.
- client: fix crashing bug.
Deleting records in ~COPROCS() was bad,
since we copy HOST_INFO to APP_INIT_DATA,
leading to a double deletion.

20) Message boards : Graphics cards (GPUs) : GPUGRID and ATI (Message 16997)
Posted 5099 days ago by Profile Paul D. Buck
Great news, indeed! If you haven't done already, tell AMD that their help and hardware are greatly appreaciated in the world of BOINC :)

MrS

Even better point out that the more projects that run ATI applications that work decently, the more cards they will sell to this small, but intense market ... I know I am solidly in the ATI camp and am down to my last couple of Nvidia cards as we type/read ... and if they stay ahead of Nvidia will stay ATI for some time ...

I can see that some of the bigger ranchers have 20-30 systems and they tend to stick with the same cards if they can find one that works well ...

We are not a big as the gamers segment (yet), but 300,000 users world wide is not a trivial market to ignore either ...


Previous 10 | Next 10
//