. . It is normal for SoG to fully utilise one CPU core for each task running on your GPU. If you want to change that turn "Sleep" on with the command -use sleep in your command line file, "mb_cmdline_win_x86_SSE3_OpenCl_NV_SoG.txt" if you have an Nvidia GPU.

I wonder that the task priority is put on "high" instead of "low". It's a bug or a feature?
Running Win 10 with setiathome-8.22_windows_intelx86__opencl_nvidia_SoG.exe
Inside cc_config.xml I use the param: <process_priority_special>1</process_priority_special>

task priority is put on "high" instead of "low". It's a bug or a feature?
...

[This is a great stream to watch. I don't have to talk much; I can learn a lot. Thanks to all.]

In directory BOINC/slots/x (used by S@H), I see (line 4 for me): "Priority of worker thread raised successfully"

If it's a short explanation: What does this mean and what's the impact on my computer?

[The answer about "line -hp in file "mb_cmdline-8.22_windows_intel__opencl_nvidia_SoG.txt"." is ... maybe an answer to a different question? That set of files (one per application) has zero length on my system until I put something in it.]

task priority is put on "high" instead of "low". It's a bug or a feature?
...

[This is a great stream to watch. I don't have to talk much; I can learn a lot. Thanks to all.]

In directory BOINC/slots/x (used by S@H), I see (line 4 for me): "Priority of worker thread raised successfully"

If it's a short explanation: What does this mean and what's the impact on my computer?

[The answer about "line -hp in file "mb_cmdline-8.22_windows_intel__opencl_nvidia_SoG.txt"." is ... maybe an answer to a different question? That set of files (one per application) has zero length on my system until I put something in it.]

The SETI GPU/CPU tasks have an inherent System Idle Priority as written. They leave the CPU tasks alone which run at Idle System Priority, but bump up the GPU tasks by default to the next highest level above Idle, which is Below Normal System Priority so they get a little more timeslices since they need to be fed regularly by the CPU. You can alter the priority of the tasks either by calling out -hp in the "mb_cmdline-8.22 ~~platform~~.txt file which is delivered blank and ready for customization. Or you can call out a commandline parameter in a app_config file too as an alternative way to alter the task running priority. Another way to alter the stock priority level is with third-party apps like ProcessLasso to make any application run at whatever priority level you desire. The stock applications try to put the least amount of demand on the CPU/GPU resources to accommodate lesser hardware platforms. You just see the output of the GPU app stderr.txt showing the bump in process priority at each loading of a new task. The developers choose how they want their app to run. Some apps have considerable parameters that you can choose to alter the way the app runs on your system. Some apps are pretty locked down in how they can be run. When all else fails .... read the README.TXT files for each app to see what choices you have in running the task app.Seti@Home classic workunits:20,676 CPU time:74,226 hours

. . I am toying around with Linux and it is a very strange land. Does the SoG or SaH app in Linux respond to the commandline file as with the Windows version? And what is the naming protocol? There is no blank template there to work off.

. . I am toying around with Linux and it is a very strange land. Does the SoG or SaH app in Linux respond to the commandline file as with the Windows version? And what is the naming protocol? There is no blank template there to work off.

Stephen

??

Good question Stephen.
I reprted this over at Lunatics but never got a good answer for it
I did some apha testing with different OpenCL apps on Mint 17.x.
To be honest i never got the app args working from comand line text file.
So i use either the cc_config.xml or appinfo.xml to adjust the comands.

Not using mb_cmdline.txt-file, using commandline options.
Number of period iterations for PulseFind set to 30
Running on device number: 0
Maximum single buffer size set to:384MB
SpikeFind FFT size threshold override set to:2048
TUNE: kernel 1 now has workgroup size of (64,1,4)
oclFFT global radix override set to:256
oclFFT local radix override set to:16
oclFFT max WG size override set to:256
oclFFT max local FFT size override set to:512
oclFFT number of local memory banks set to:32
oclFFT minimal memory coalesce width set to:32
Running on device number: 0With each crime and every kindness we birth our future.

. . I am toying around with Linux and it is a very strange land. Does the SoG or SaH app in Linux respond to the commandline file as with the Windows version? And what is the naming protocol? There is no blank template there to work off.

Stephen

??

Good question Stephen.
I reprted this over at Lunatics but never got a good answer for it
I did some apha testing with different OpenCL apps on Mint 17.x.
To be honest i never got the app args working from comand line text file.
So i use either the cc_config.xml or appinfo.xml to adjust the comands.

Not using mb_cmdline.txt-file, using commandline options.
Number of period iterations for PulseFind set to 30
Running on device number: 0
Maximum single buffer size set to:384MB
SpikeFind FFT size threshold override set to:2048
TUNE: kernel 1 now has workgroup size of (64,1,4)
oclFFT global radix override set to:256
oclFFT local radix override set to:16
oclFFT max WG size override set to:256
oclFFT max local FFT size override set to:512
oclFFT number of local memory banks set to:32
oclFFT minimal memory coalesce width set to:32
Running on device number: 0

. . Well I have heard scary things about playing with ap_info.xml so I might give that a miss but I am hoping cc_config.xml is much like ap_config.xml and fairly safe to use.

Recently I got 4 WU with computation errors using this app: SETI@home v8 v8.22 (opencl_ati5_SoG_nocal) windows_intelx86.
Here is one example: https://setiathome.berkeley.edu/result.php?resultid=5618949723
All on the same host, running default apps. Its with a FuryX GPU and gets consistently good results for SETI@home v8 v8.22 (opencl_ati5_nocal)Instagram: rpc_labs

All of my Intel GPU work failed to finish completely. One of the WU is located at https://setiathome.berkeley.edu/result.php?resultid=5620728108.
According to the error message, it seems it could not open a binary kernel file. Something wrong or missing in my computer?

Ive been running the optimized SETI 8.22 app from Mike's World website for a week now (without any other changes) and i dont see much improvement compared to the standards SETI apps.
Seeing the posts below on cmdline arguments, im wondering if some tweaking of app_config.xml would benefit the execution speed. BTW: currently i dont have a app_config.xml in my BOINC/SETI folder, so i have to start from scratch.

SETI WIKI provides explanation on different arguments in app_config.xml, but does not specify default values. Ive tried searching the forum, but there appears not to be a clearcut guide on what settings are good for my systems. Any guidance is appreciated!