Hmm. Guess xj didn't totally drive a stake through the heart of that particular issue ... Personally, haven't had that since I loaded it ...

xj dates from around 21 April. Raistmer's SoG r3430 dates from 31 March, so it's not really fair to blame him for not including that fix in advance. But it is a reminder that we perhaps need to consider 'hardening' SoG against this problem, if that's going to become part of the armoury for handling VLAR on Main.

End of GBT VLAR fun it seems. Only Arecibo tasks downloading now.

Hmm. Guess xj didn't totally drive a stake through the heart of that particular issue ... Personally, haven't had that since I loaded it ...

xj dates from around 21 April. Raistmer's SoG r3430 dates from 31 March, so it's not really fair to blame him for not including that fix in advance. But it is a reminder that we perhaps need to consider 'hardening' SoG against this problem, if that's going to become part of the armoury for handling VLAR on Main.

Sorry, missed that it was a different app ... no intent to assign blame ...

---

If I can help out by testing something, please let me know.
Available hardware and software is listed in my profile here.

Tut,

How much CPU of your 8 core were those 3 work units using?

Tut,

How much CPU of your 8 core were those 3 work units using?

Well, if they are GBT VLAR's, they use almost one core/thread each (95-99%). However I only run 3 CPU WU's, so 2 cores/threads are always free.
Even "normal" AR's use lots of CPU with opencl_nvidia_SoG, or opencl_nvidia_sah, some of them almost a full core/thread, but usually from 40-80%. Only shorties use under 10% of a core/thread.
I don't want to use sleep, because it really hits the performance. I can live with the high CPU usage.

That is what I was seeing as well.

Since I was running multiple GPUs in mine, was forced to have -use_sleep in mine, really only extended the time by a few minutes.

But like you, I want those few minutes, lol..

My problems, not enough CPU cores for all the GPU work units.

Just encountered a "finish file present too long" error on Arecibo mid-AR task 23790517 - it was sharing the GTX 970 with a guppi VLAR, running SoG r3430.

Timetable was

11:03:17 (40088): called boinc_finish(0)
08/05/2016 11:03:30 | SETI@home Beta Test | [sched_op] Reason: Unrecoverable error for task 24mr10ac.7768.9486.6.40.124_1
08/05/2016 11:03:35 | SETI@home Beta Test | Computation for task 24mr10ac.7768.9486.6.40.124_1 finished

So it looks as if there was an 18-second gap between calling finish and the app quitting, with BOINC pulling the plug at 13 seconds.

GPU device sync requested... ...GPU device synched
11:03:17 (40088): called boinc_finish(0)

app completely finished its own operation.
Worth to rise this case in front of BOINC API writers.

---

News about SETI opt app releases: https://twitter.com/Raistmer

Hmm, I think we're about to run out of tasks....

Tasks ready to send 1339.

http://setiweb.ssl.berkeley.edu/beta/server_status.php

Time to move back to main perhaps.

I don't understand why Eric (and/or other admins) want to send GBT .vlar tasks to GPUs.
With the currently mix of Arecibo and GBT tasks at Main, there is no problem to feed e.g. my PC (example for a fast PC) for 24/7.

Or Arecibo tasks will run out, just GBT tasks will come in future?
How will look the mix in future?

Answer is given. It's no work or slow work choice. Not slow work or fast work one.

But the above mentioned tasks lasts just around 30 secs (hard to find time differences).

Indeed, existing PGv8 set is too fast for high-end cards.
So I would recommend for now to take one GUPPI VLAR task from here or main, to put it into bench and use it for tuning.
If VLAR is "our new future" then it make sence to do best optimization under very VLAR task.

Since a few days I have 34 °C ambient in the 'PC room'.
And not very healthy CPU/GPU temps.
So I switched off my quad FuryX PC, at least for two weeks, because of construction work in front/opposite of/to the house (not possible to open the windows during the day), and to think about a way to cool down more the 'PC room'.
More pull out fans into the window or installation of an A/C.


Then, it would be equal to use a 'guppi' .vlar or a .vlar task for bench test runs?
Or it would be better to use a 'guppi' .vlar task?
If equal, maybe I start to use the VLAR task of the 'PG WU set v8'. ;-)
(Until now I have no idea how long this VLAR task will lasts.)


Because of...

postid=58192
I would like to make bench test runs (I guess - because after nearly 1 year it's still not possible to let run 2 WUs/GPU on my FuryX's with the currently available drivers - this will not change in future, now I could start to make bench test runs for to find opti cmdline settings for AP and MB), but until now I didn't found the correct tools on the Lunatics site.

I used:
MBbench 2.10
PG WU set v8 (all tasks without the VLAR task)
WisGen WUs.7z (the _WisGenA.wu)

For long time as I made AstroPulse bench test runs on my J1900 (iGPU + GT730) PC, I inserted the app with a few different cmdline settings (in BenchCfg.txt), after execution of the .cmd file the tool created the .wisdom file at (with) the 1st (cmdline line), and all other following cmdline (lines) settings the task (.wisdom creation) run were skipped, and then the 'real' bench test run started with the test tasks.

With the above mentioned MBbench 2.10 for SETI tasks, it don't create a .wisdom file automatically. (I don't know what to do with the files of 'MBBench v2.13' (it looks like it will suspend 3 CPU tasks and make GPU bench test?))

I used _WisGenA.wu, made a copy of it named it _WisGenB.wu - and this two tasks in the folder TestWUs.

Then this both tasks were used for to create the .wisdom file and all other files (*.bin_V7_*, .bin_*****VM).
Then the 3 'real' test tasks were calculated.
But the above mentioned tasks lasts just around 30 secs (hard to find time differences).


Could someone of the Lunatics crew make 'new' 'longer' bench test tasks (for fast GPUs)?
Maybe 2 mins VHAR, 4 mins mid-AR and 6 mins ('guppi') VLAR tasks?
So that they are good (and have everything) for to make bench test runs (on fast GPUs) for to find fastest cmdline settings. This would be very helpful and I would be very grateful.

Like I described above, with the 'MBbench 2.10' it don't work like with 'APbench211_minimal' (here is the #ap_genwis.dat file included) in past.

If I would continue with the work around way like above mentioned, task #1 and #2 the _WisGenA.wu, for to create the .wisdom file (2nd run of a task, .wisdom file creation finished), this would be waste of time... - or how would it work with 'MBbench 2.10'?
I copy the VHAR, 2x mid-AR and VLAR task into the TestWUs folder.
_WisGenA.wu and _WisGenB.wu (copy of *A*) also into the TestWUs folder.

If I have e.g. in the BenchCfg.txt file:
MB8_win_x86_SSE2_OpenCL_ATi_HD5_r3330.exe -bla bla -bla bla
MB8_win_x86_SSE2_OpenCL_ATi_HD5_r3330.exe -bla bla2 -bla bla2
MB8_win_x86_SSE2_OpenCL_ATi_HD5_r3330.exe -bla bla3 -bla bla3

...then the _WisGenA.wu and _WisGenB.wu runs at line #2 and #3 are for nothing, needless.
Or how it would work?


Raistmer, could you (the whole Lunatics crew, and/or advanced SETI members) make a description how to make bench test runs (maybe at the Main or Lunatics Forum)?
All possible commands, which numbers possible, if they are connected or alone and possible changes?
E.g. for AP:
-unroll N, 1 to 100, alone, +/- 1
-ffa_block N and -ffa_block_fetch N, 512 to 20480, connected, +/- 64

E.g. for AP and VGA card series with recommendations for testing:
Low end (NV GT***, AMD R5):
-unroll N, 1 to 10, alone, +/- 1
High end (NV GTX*80, AMD R9):
-unroll N, 10 to 20, alone, +/- 1

How much tasks/GPU (just for NV).

This would be very helpful and I (I guess many others also) would be very grateful.

Thanks.

---

No plan to pass 8.12 to production to Seti@Home??

yep, there are such plans. Next week or maybe after.

:-P

Are we going to have a VLAR/No VLAR to GPU, switch test on Beta soon?

Are we going to have a VLAR/No VLAR to GPU, switch test on Beta soon?

I'd like to see something like this,too.

---

Well, there's not much happening here. I'm back running Beta with my GTX980. 100% Beta, GPU only. Nothing on main.

Computer 75292

Well, there's not much happening here. I'm back running Beta with my GTX980. 100% Beta, GPU only. Nothing on main.

Computer 75292

For what reason? There is no GPU apps in beta testing right now, all of them already released.

---

News about SETI opt app releases: https://twitter.com/Raistmer

Well, there's not much happening here. I'm back running Beta with my GTX980. 100% Beta, GPU only. Nothing on main.

Computer 75292

For what reason? There is no GPU apps in beta testing right now, all of them already released.

For the reason of doing some crazy testing only. Remember, I'm Swedish :-)

I set a Windows 10 client running on Beta on 1 May (BOINC version 7.6.22). Since then I have had 39 invalid tasks and 2 errors, all on Intel GPU (v8.12) tasks.

The invalid tasks I have checked have all been non-guppi and the wingmen' tasks have completed and validated.

Not sure if this is something significant or not so thought I would report it

http://setiweb.ssl.berkeley.edu/beta/results.php?hostid=78787

Was wondering if the bulletin regarding 4 bit WUs we received meant that new Beta work needs to be crunched? It seemed a bit unclear, to me at least ...

---

If I can help out by testing something, please let me know.
Available hardware and software is listed in my profile here.

Was wondering if the bulletin regarding 4 bit WUs we received meant that new Beta work needs to be crunched? It seemed a bit unclear, to me at least ...

Well, as I understand it, that means that the project wants us Beta testers to test these new 4-bit Guppi tasks.

So yes, Beta work needs to be crunched.

I set a Windows 10 client running on Beta on 1 May (BOINC version 7.6.22). Since then I have had 39 invalid tasks and 2 errors, all on Intel GPU (v8.12) tasks.

The invalid tasks I have checked have all been non-guppi and the wingmen' tasks have completed and validated.

Not sure if this is something significant or not so thought I would report it

http://setiweb.ssl.berkeley.edu/beta/results.php?hostid=78787

Try another driver version - will it help?

---

News about SETI opt app releases: https://twitter.com/Raistmer

I set a Windows 10 client running on Beta on 1 May (BOINC version 7.6.22). Since then I have had 39 invalid tasks and 2 errors, all on Intel GPU (v8.12) tasks.

The invalid tasks I have checked have all been non-guppi and the wingmen' tasks have completed and validated.

Not sure if this is something significant or not so thought I would report it

http://setiweb.ssl.berkeley.edu/beta/results.php?hostid=78787

Try another driver version - will it help?

Thanks for the suggestion, Raistmer.

I've rolled back to an older version. Will run for a few days, to see if that stops the invalids/errors, and report back