Forum > Discussion Forum

What BOINC features we need and what don't

<< < (2/4) > >>

Raistmer:

--- Quote from: arkayn on 18 Jul 2009, 05:58:38 pm ---
--- Quote from: Raistmer on 18 Jul 2009, 03:26:22 pm ---situation 1:
MW has lower project share than SETI.
BOINC tends to run 5 SETI tasks (quad system with ncpus setted to 4) that suboptimal and no MW tasks at all, that too unoptimal to tolerate, GPU stays completely idle.


--- End quote ---

I think I know why mine works a bit better than yours on MW, I don't use the config file and just let it run as needed.
Recently I have gotten a lot of work and while it will start up 10 units it leaves the rest as "ready to start"

Of course I also drop down to 3 processing SETI as well.

--- End quote ---
Hm, if you get idle CPU cores time to time it's not better ;)
Currently I managed to have MW RAC >52k with peak >56k (then einstein started in high priority mode and BOINC with great sadism began to put into waiting state exactly that MW tasks which was actually run) It's MW opt app pecularity so I didn't mention it in starting post but if those 3 (in my case number ==3, default setting) MW tasks that actually run will be put in waiting state, all MW tasks will be stopped. BOINC can set remaining "running" tasks into high priority  state - no matter. They will do no progress at all.
User intervention (BOINC restart) absolutely required in such situation.

arkayn:
I go full idle on occasion, it is also my gaming machine and playing games and crunching at the same time do not mix at all.
Either the ATI app crashes, the driver crashes or the computer just BSOD's.

I don't mind the idle CPU all that much since I am mostly concentrating on getting my MW RAC up.

Raistmer:
Ok, so we pursue different aims in our setups :)
I trying to get best possible MW performance (almost pure ATI GPU processing) almost not hurting SETI performance (CPU processing).
And came to sad conclusion that it's impossible to achieve with BOINC 6.6.36.
Sheduling is broken. High priority mode in use on every sneeze... And running 4 CPU taks in high priority mode makes impossible to run additional tasks even with avg_cpu setted to 0.01.
So, if 4 SETI or einstein tasks are running in high priority mode, no MW tasks running at all :(
Situation with BOINC resembles situation with robots described in Shekly's story "A Ticket to Tranai".... they unfeature their robots in same manner BOINC devs degrade BOINC... :(

arkayn:
Lets also not forget that I only use 6.6.20 on my PC's as well.

Raistmer:

--- Quote from: arkayn on 21 Jul 2009, 08:32:03 am ---Lets also not forget that I only use 6.6.20 on my PC's as well.

--- End quote ---
Oh, you lucky one :)
I installed some special build of 6.6.36 to diminish current SETI's problems with bandwidth, but it seems will be forced to return to 6.6.20. I used it before and had only one problem - too much running MWs.... Now I have completely different problem, no MWs at all too often...

Navigation

[0] Message Index

[#] Next page

[*] Previous page