Welcome to MilkyWay@home

Posts by blox

1) Message boards : Application Code Discussion : Milkyway 0.23 (ati13ati) (Message 45559)
Posted 14 Jan 2011 by blox
Post:
I was able to read that paragraph..well done me :-)
2) Message boards : Application Code Discussion : Increasing the number of allowed CPUs (Message 45553)
Posted 13 Jan 2011 by blox
Post:
Oooh so cynical :-) , I suppose that's better than gullible..

You mean to say they are deliberately slowing the pace for some reason? Implying they have a vested interest in delaying the project?
3) Message boards : Application Code Discussion : Increasing the number of allowed CPUs (Message 45549)
Posted 13 Jan 2011 by blox
Post:
I recompiled the client and hard coded 10,000 cpus, so as to get a decent cache in case of server problems, but it's topping out at 96 WU.

There is an option in the project config.xml file -

<max_ncpus>N</max_ncpus> - An upper bound on NCPUS (default: 16)

Would the admins consider upping this limit so that those who want to can use this method of increasing the cache so that more work can be done?

On my 4 GPU system, I need 5530 cpus to get a 3-day cache.
4) Message boards : Number crunching : Getting more than 18 work units at a time (Message 44928)
Posted 11 Dec 2010 by blox
Post:
It mostly works but with some problems.

I had a look at that link.. and that was the only host that had any invalid WU.

Today there are 2 invalid WU, both from the same host, and none for any other host. Perhaps it is crashing, I'm using 6.12.

The biggest problem I am having atm is most of my saved WU abort with message "aborted by project", which seems to mean that the WU was successful on 2 hosts.. and if I started the WU it would be wasted.

So too big a cache=no point in caching as the WU has already been done, which leads to usually just 1 task being freshly downloaded and my other 3 GPU idling for a few minutes.

Perhaps there is some way to report a larger no of CPU to Boinc...

5) Message boards : Number crunching : Getting more than 18 work units at a time (Message 44849)
Posted 9 Dec 2010 by blox
Post:
Yes, but you can use multiple data dirs one after the other
6) Message boards : Number crunching : Getting more than 18 work units at a time (Message 44829)
Posted 8 Dec 2010 by blox
Post:
In the last 3 days I have done about double my usual AC :D
7) Message boards : Number crunching : boinc --allow_multiple_clients (Message 44782)
Posted 7 Dec 2010 by blox
Post:
I've written a guide.. and allowed non-members to view(I hope)

http://www.overclock.net/blogs/blox/2050-bloxcache-boinc-caching-batch-file-initialisation.html

http://www.overclock.net/blogs/blox/2051-bloxcache-boinc-caching-batch-file-running.html

8) Message boards : Number crunching : Getting more than 18 work units at a time (Message 44781)
Posted 7 Dec 2010 by blox
Post:
I've written a guide.. and allowed non-members to view(I hope)

http://www.overclock.net/blogs/blox/2050-bloxcache-boinc-caching-batch-file-initialisation.html

http://www.overclock.net/blogs/blox/2051-bloxcache-boinc-caching-batch-file-running.html

9) Message boards : Number crunching : Getting more than 18 work units at a time (Message 44735)
Posted 6 Dec 2010 by blox
Post:
Chaul - did you check out my idea?

It's mostly working atm.. but it's not cycling through the instances properly.

the idea is: Have multiple boinc data dirs and switch between them so each maintains a cache.

My current problem is when I kill the instance of boinc it doesnt resume a WU where it left off.. it starts again.. so increased time per instance is beneficial.. but not too much or deadline is passed
10) Message boards : Number crunching : Getting more than 18 work units at a time (Message 44713)
Posted 5 Dec 2010 by blox
Post:
poss workaround..

this is my current idea http://www.overclock.net/blogs/blox/2046-bloxcache-boinc-caching-batch-file.html

The main problem atm, is that the --exit_after_app_start switch doesn't seem to be hnored all the time.. and max value seems to be 90.

Also any half processed wu are restarted at 0, so a bit of a waste.

Any ideas?

Cheers,
Rick
11) Message boards : Number crunching : boinc --allow_multiple_clients (Message 44712)
Posted 5 Dec 2010 by blox
Post:
Thanks Mike.. I have been trying to think of a workaround..

this is my current idea http://www.overclock.net/blogs/blox/2046-bloxcache-boinc-caching-batch-file.html

The main problem atm, is that the --exit_after_app_start switch doesn't seem to be hnored all the time.. and max value seems to be 90.

Also any half processed wu are restarted at 0, so a bit of a waste.

Any ideas?

Cheers,
Rick
12) Message boards : Number crunching : boinc --allow_multiple_clients (Message 44204)
Posted 24 Nov 2010 by blox
Post:
I had my BOINC settings at 50% CPUs so I was only getting 36 WU, upped it to 75%(9) and now get 54.. a big improvement...

but why is it limited on no of CPU?.. we're in GPU land now.

even with 54 WU, my 4 GPU@1Ghz can do that in 90 min. This doesn't help us contribute to the awesome MW project when the servers are down. We all need to have at least 24 hrs of WU we can crunch while the servers are not responding. It's wasting our time and resources. And my room was freezing this morning as WU = processing = waste heat = toasty room :)

Please admins/progs, lets work to giving each client enough WU to survive a 24hr outage of the servers... this = more WU total, which is a good thing.. Unless we are going to run out of WU soon :(

Hope you have a new project planned if that is the case

Rock on
13) Message boards : Number crunching : boinc --allow_multiple_clients (Message 43988)
Posted 20 Nov 2010 by blox
Post:
My 920 + 4870x2 often limits at 48 (6x8) tasks.. 980x + 2 x 5970 never gets to the limit

I am running each new boinc in a separate dir, and have a cc_config and rpc_gui_auth in each. The cc_config ignores the 3 other GPUs, e.g. 0 ignores 1,2,3

HT is on, 12 cores available
14) Message boards : Number crunching : boinc --allow_multiple_clients (Message 43984)
Posted 20 Nov 2010 by blox
Post:
Hi,

what's going on with the MW scheduling? My dual 5970(1000/1200, 1.25V) never seems to have enough WU.

I tried setting up some new client dirs and running

c:
cd "c:\program files (x86)\boinc"
boinc --allow_multiple_clients --detach --dir c:\programdata\boinc0 --gui_rpc_port 5000
boinc --allow_multiple_clients --detach --dir c:\programdata\boinc1 --gui_rpc_port 5001
boinc --allow_multiple_clients --detach --dir c:\programdata\boinc2 --gui_rpc_port 5002
boinc --allow_multiple_clients --detach --dir c:\programdata\boinc3 --gui_rpc_port 5003

Thinking that this would be like I had each GPU in a separate rig.. so would get a cache per GPU.

Everything seems to work, but all 4 new boincs are seen as the same client(despite different IDs) when it comes to checking MW for work, as I get "last request too soon"(or similar)

How can I tell MW to only check for work every 5 min?

Thanks to the programmers

Thx
Blox




©2024 Astroinformatics Group