Posts by Ageless

21) Questions and Answers : GPU applications : Trouble trying to get multiple WU per GPU on a multi GPU system (Message 1847603)
Posted 16 days ago by Profile Ageless
Post:
I know you fixed it already, this is just for the next person with the same problem:
app_config.xml.txt
Right-click on the file name, from the drop-down menu choose Rename. Scroll to the end of the line, use backspace four times to remove the dot tee ex tee (.txt), and finish with Enter.
22) Questions and Answers : GPU applications : Trouble trying to get multiple WU per GPU on a multi GPU system (Message 1847560)
Posted 16 days ago by Profile Ageless
Post:
Where did you put the cc_config.xml file? It needs to be in the BOINC data directory, default at C:\Programdata\BOINC\
Make sure the file is called cc_config.xml, not that it got an extra extension.
Hope you made it with Notepad, as making it with any other text editor will add invisible characters that BOINC won't like.

A very easy way to get a fully populated cc_config.xml file in the right place is to open BOINC Manager->Advanced view->Options->Event Log options...->uncheck task->OK.
Do enable task again after this, BOINC Manager->Advanced view->Options->Event Log options...->check task->OK.

You have to restart both the BOINC Manager (GUI) and the client, as GPU detection decisions are only done at BOINC (client) startup.

The app_config.xml file also needs to be written in Notepad and not any other text editor, as those add invisible characters BOINC doesn't like.
It is stored in C:\Programdata\BOINC\projects\setiathome.berkeley.edu\

When writing or editing XML files in Notepad, save them as follows, i.e. app_config.xml:
File->Save as..->Filename app_config.xml ->save as type: All files (*.*) ->Encoding ANSI
23) Questions and Answers : Macintosh : All my tasks result in computational errors. (Message 1847551)
Posted 16 days ago by Profile Ageless
Post:
No, it's not the same as above. The problem is detailed in the error message that you posted yourself:
WARNING: This application needs newer GPU, at least ATI Radeon HD 5000 needed, exiting !

The minimum required AMD/ATI GPU for this project for the Mac is a HD 5000.
It may be weird you're getting work for it, as that is a thing that the server should read and decide upon not to send you work. - Edit: having looked that up, that's only done for CPUs, not for GPUs.

But in any case, best set in project preferences not to use the ATI GPU.
24) Questions and Answers : GPU applications : Tuning up twin GTX 750 Ti's (Message 1847546)
Posted 16 days ago by Profile Ageless
Post:
Goes into the ap_cmdline_win_*.txt file for OpenCL Astropulse. Probably called something like ap_cmdline-710_windows_intel__opencl_nvidia.txt or similar.
Default directory: C:\Programdata\BOINC\projects\setiathome.berkeley.edu\

AstroPulse OpenCL application currently available in 3 editions: for AMD/ATi, nVidia and Intel GPUs.
It's intended to process SETI@home AstroPulse v7 tasks.

Source code repository: https://setisvn.ssl.berkeley.edu/svn/branches/sah_v7_opt
Build revision:2742
Date of revision commit: 2014/11/02 19:58:47

Available command line switches:
-v N :sets level of verbosity of app. N - integer number. -v 0 disables almost all output. Default corresponds to -v 1. 
	Levels from 2 to 5 reserved for increasing verbosity, higher levels reserved for specific usage. 
	-v 2 enables all signals output.
	-v 3 additionally to level 2 enables output of simulated signals corresponding current threshold level (to easely detect near-threshold validation issues).
	-v 6 enables delays printing where sleep loops used.
	-v 7 enables oclFFT config printing for oclFFT fine tune.
	-v 8 enables allocated GPU memory printing for different parts of algorithm

-ffa_block N :sets how many FFA's different period iterations will be processed per kernel call. N should be integer even number less than 32768.
Increase in this param's value will increase app's GPU memory consumption.
-ffa_block_fetch N: sets how many FFA's different period iterations will be processed per "fetch" kernel call (longest kernel in FFA).
N should be positive integer number, should be divisor of ffa_block_N.

-unroll N :sets number of data chunks processed per kernel call in main application loop. N should be integer number, minimal possible value is 2.
Increase in this param's value will increase app's GPU memory consumption.

-skip_ffa_precompute : Results in skipping FFA pre-compute kernel call. Affects performance. Experimentation required if it will increase or decrease performance on particular GPU/CPU combo.

-exit_check :Results in more often check for exit requests from BOINC. If you experience problems with long app suspend/exit use this option.
Can decrease performance though.

-use_sleep :Results in additional Sleep() calls to yield CPU to other processes. Can affect performance. Experimentation required.

-initial_ffa_sleep N M: In PC-FFA will sleep N ms for short and M ms for large one before looking for results. Can decrease CPU usage.
Affects performance. Experimentation required for particular CPU/GPU/GPU driver combo. N and M should be integer non-negative numbers.
Approximation of useful values can be received via running app with -v 6 and -use_sleep switches enabled and analyzing stderr.txt log file.

-initial_single_pulse_sleep N : In SingleFind search will sleep N ms before looking for results. Can decrease CPU usage.
Affects performance. Experimentation required for particular CPU/GPU/GPU driver combo. N should be integer positive number.
Approximation of useful values can be received via running app with -v 6 and -use_sleep switches enabled and analyzing stderr.txt log file.

-sbs N :Sets maximum single buffer size for GPU memory allocations. N should be positive integer and means bigger size in Mbytes.
For now if other options require bigger buffer than this option allows warning will be issued but memory allocation attempt will be made.

-hp : Results in bigger priority for application process (normal priority class and above normal thread priority).
Can be used to increase GPU load, experimentation required for particular GPU/CPU/GPU driver combo.

-cpu_lock : Enables CPUlock feature. Results in CPUs number limitation for particular app instance. Also attempt to bind different instances to different CPU cores will be made.
Can be used to increase performance under some specific conditions. Can decrease performance in other cases though. Experimentation required.
Now this option allows GPU app to use only single logical CPU.
Different instances will use different CPUs as long as there is enough of CPU in the system.
To use CPUlock in round-robin mode GPUlock feature will be enabled. Use -instances_per_device N option if few instances per GPU device are needed.

-cpu_lock_fixed_cpu N : Will enable CPUlock too but will bind all app instances to the same N-th CPU (N=0,1,.., number of CPUs-1).

-gpu_lock :Old way GPU lock enabled. Use -instances_per_device N switch to provide number of instances to run.

-instances_per_device N :Sets allowed number of simultaneously executed GPU app instances per GPU device (shared with MultiBeam app instances).
N - integer number of allowed instances.

These 2 options used together provide BOINC-independent way to limit number of simultaneously
executing GPU apps. Each SETI OpenCL GPU application with these switches enabled will create/check global Mutexes and suspend its process
execution if limit is reached. Awaiting process will consume zero CPU/GPU and rather low amount of memory awaiting when it can continue execution.

-disable_slot N: Can be used to exclude N-th GPU (starting from zero) from usage.
Not tested and obsolete feature, use BOINC abilities to exclude GPUs instead.

Advanced level options for developers (some app code reading and understanding of algorithms used is recommended before use, not fool-proof even in same degree as
options above):
-tune N Mx My Mz : to make app more tunable this param allows user to fine tune kernel launch sizes of most important kernels.
	N - kernel ID (see below)
	Mxyz - workgroup size of kernel. For 1D workgroups Mx will be size of first dimension and My=Mz=1 should be 2 other ones.
	N should be one of values from this list:
	FFA_FETCH_WG=1,
	FFA_COMPARE_WG=2
	For best tuning results its recommended to launch app under profiler to see how particular WG size choice affects particular kernel.
	This option mostly for developers and hardcore optimization enthusiasts wanting absolute max from their setups.
	No big changes in speed expected but if you see big positive change over default please report.
	Usage example: -tune 2 32 1 1  (set workgroup size of 32 for 1D FFA comparison kernel).

-oclFFT_plan A B C : to override defaults for FFT 32k plan generation. Read oclFFT code and explanations in comments before any tweaking.
	A - global radix
	B - local radix
	C - max size of workgroup used by oclFFT kernel generation algorithm

Usage example:
-oclFFT_plan 64 8 256 (this corresponds to old defaults);
-oclFFT_plan 0 0 0 (this effectively means this option not used, hardwired defaults in play).

These switches can be placed into the file called ap_cmdline.txt also.

For device-specific settings in multi-GPU systems it's possible to override some of command-line options via application config file.
Name of this config file:
AstroPulse_<vendor>_config.xml where vendor can be ATi, NV or iGPU.
File structure:
<deviceN>
	<unroll>N</unroll>
	<ffa_block>N</ffa_block>
	<ffa_block_fetch>N</ffa_block_fetch>
	<oclfft_plan>
	        <size>32768</size>
		<global_radix>N</global_radix>
		<local_radix>N</local_radix>
		<workgroup_size>N</workgroup_size>
	</oclfft_plan>
	<tune>
		<tune_kernel_index>N</tune_kernel_index>
		<tune_workgroup_size_x>N</tune_workgroup_size_x>
		<tune_workgroup_size_y>N</tune_workgroup_size_y>
		<tune_workgroup_size_z>N</tune_workgroup_size_z>
	</tune>
	<initial_ffa_sleep_short>N</initial_ffa_sleep_short>
	<initial_ffa_sleep_large>N</initial_ffa_sleep_large>
	<initial_single_pulse_sleep>N</initial_single_pulse_sleep>
	<sbs>N</sbs>
	<skip_ffa_precompute>
	<no_defaults_scaling>
</deviceN>

where deviceN - particular OpenCL device N starting with 0, multiple sections allowed, one per each device.
other fields - corresponding command-line options to override for this particular device.
All or some sections can be omitted.
AstroPulse uses only one FFT size in GPU-based calculations so <size> field in <oclfft_plan> reserved to 32768 and can be omitted. To be used in MultiBeam.

For examples of app_info.xml entries look into text file with .aistub extension provided in corresponding package.

Known issues:
- With 12.x Catalyst drivers GPU usage can be low if CPU fully used with another loads.
If you see low GPU usage of zero blanked tasks try to free one or more CPU cores. *
- For overflowed tasks found signal sequence not always match CPU version.

Best usage tips:

For best performance it is important to free 2 CPU cores running multiple instances.
Freeing at least 1 CPU core is necessity to get enough GPU usage.*

* As alternate solution try to use -cpu_lock / -cpu_lock_fixed_cpu N options.
This might only work on fast multicore CPU`s.

command line parameters.
Command line switches can be used either in app_info.xml or ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt.
Params in ap_cmdline*.txt will override switches in <cmdline> tag of app_info.xml.
_______________________

High end cards (more than 30 compute units)

-unroll 18 -ffa_block 16384 -ffa_block_fetch 8192

* Bigger unroll values < 20 doesn`t necessarily result in better run times.

Mid range cards (l12 - 24 compute units)

-unroll 12 -ffa_block 12288 -ffa_block_fetch 6144

entry level GPU (less than 6 compute units)

-unroll 4 -ffa_block 2048 -ffa_block_fetch 1024

-tune switch

possible values:

-tune 1 256 1 1
-tune 1 128 2 1
-tune 1 64 4 1
-tune 1 32 8 1
-tune 1 16 16 1

Intensive testing highlighted -tune 1 64 4 1 and -tune 1 32 8 1 to be fastest on HD 7970 and R9 280X.
Further testing required for other GPU`s.

-oclFFT_plan switch

Use at your own risk !
------------------------

FFT kernels are processed in 8 point fft kernels by default.
Using different fft kernel planning can speed up processing significantly.
In most cases 16 point fft kernels are fastest for Astropulse V7.

-oclFFT_plan 256 16 256

Example:

High end cards
-unroll 18 -oclFFT_plan 256 16 256 -ffa_block 16384 -ffa_block_fetch 8192 -tune 1 64 4 1 -tune 2 64 4 1

Mid range cards
-unroll 12 -oclFFT_plan 256 16 256 -ffa_block 12288 -ffa_block_fetch 6144 -tune 1 64 4 1 -tune 2 64 4 1

Your mileage might vary.
-----------------------------------------------------

App instances.
______________

On HD 7950/7970, R9 280X running 2 instances should be fastest.
On R9 290X running 3 instances should be easily possible. Further testing required.

On mid range cards HD 5770, 6850/6870, 7850/7870 and R8 best performance should be running 2 instances.

If you experience screen lags reduce unroll factor and ffa_block_fetch value.

Addendum:
_________

Running multiple cards in a system requires freeing another CPU core.
25) Questions and Answers : GPU applications : Tuning up twin GTX 750 Ti's (Message 1847544)
Posted 16 days ago by Profile Ageless
Post:
Goes into the mb_cmdline_win_*.txt file for OpenCL Multibeam. Probably called something like mb_cmdline-8.22_windows_intel__opencl_nvidia_SoG.txt or similar.
Default directory: C:\Programdata\BOINC\projects\setiathome.berkeley.edu\

MultiBeam OpenCL application is intended to process SETI@home MultiBeam v6, v7, v8, and forthcoming "large" tasks.

Source code repository: https://setisvn.ssl.berkeley.edu/svn/branches/sah_v7_opt
Build from SVN revision: 3330
Date of revision commit: 2016/01/09 14:55:56

Available command line switches:

-v N : sets level of verbosity of app. N - integer number.
       Default corresponds to -v 1. 

    -v 0 disables almost all output.
         Levels from 2 to 5 reserved for increasing verbosity, higher levels reserved
         for specific usage.
    -v 2 enables all signals output.
    -v 6 enables delays printing where sleep loops used.
    -v 7 enables oclFFT config printing for oclFFT fine tune.

-period_iterations_num N : Splits single PulseFind kernel call to N calls for longest PulseFind calls. Can be used to reduce GUI lags or to prevent driver restarts. Can affect performance. Experimentation required. The default value for v6/v7/v8 tasks is N=20. N should be positive integer.

-spike_fft_thresh N : Sets threshold FFT size where switch between different SpikeFind algorithms occurs.

-sbs N : Sets maximum single buffer size for GPU memory allocations. N should be positive integer and means bigger size in Mbytes. Can affect performance and total memory requirements for application to run. Experimentation required.

-hp : Results in bigger priority for application process (normal priority class and above normal thread priority). Can be used to increase GPU load, experimentation required for particular GPU/CPU/GPU driver combo.

-cpu_lock : Results in CPUs number limitation for particular app instance. Also attempts to bind different instances to different CPU cores will be made. Can be used to increase performance under some specific conditions. Can decrease performance in other cases though. Experimentation required.

-total_GPU_instances_num N : To use together with -cpu_lock on multi-vendor GPU hosts.
Set N to total number of simultaneously running GPU OpenCL SETI apps for host (total among all used GPU of all vendors). App needs to know this number to properl select logical CPU for execution in affinity-management (-cpu_lock) mode. Should not exceed 64.

-cpu_lock_fixed_cpu N : Will enable CPUlock too but will bind all app instances to the same N-th CPU (N=0,1,.., number of CPUs-1).

-no_cpu_lock : To disable affinity management (opposite to -cpu_lock option). For ATi version CPUlock affinity management enabled by default.

-use_sleep : Results in additional Sleep() calls to yield CPU to other processes. Can affect performance. Experimentation required.

-use_sleep_ex N : enables use_sleep; sets argument of Sleep() call to N: Sleep(N)

-no_caching : Disables CL files binary caching

Here some already obsolete options are listed. They are not tested for proper operation
with latest builds and are only listed for completeness:

-gpu_lock : Old way GPU lock enabled. Use -instances_per_device N switch to provide number of instances to run.

-instances_per_device N : Sets allowed number of simultaneously executed GPU app instances (shared with AstroPulse app instances).
N - integer number of allowed instances. Should not exceed 64.

These 2 options used together provide BOINC-independent way to limit number of simultaneously executing GPU apps. Each SETI OpenCL GPU application with these switches enabled will create/check global Mutexes and suspend its process execution if limit is reached. Awaiting process will consume zero CPU/GPU and rather low amount of memory awaiting when it can continue execution.

-tune N Mx My Mz : to make app more tunable this param allows user to fine tune kernel launch sizes of most important kernels.
	
      N            - kernel ID (see below)
      Mxyz         - workgroup size of kernel. For 1D workgroups Mx will be size of
                     first dimension and My=Mz=1 should be 2 other ones.
	
      N should be one of values from this list:
	  TRIPLET_HD5_WG=1, 

For best tuning results its recommended to launch app under profiler to see how particular WG size choice affects particular kernel. This option mostly for developers and hardcore optimization enthusiasts wanting absolute max from their setups. No big changes in speed expected but if you see big positive change over default please report.
Usage example: -tune 1 2 1 64 (sets workgroup size of 128 (2x1x64) for TripletFind_HD5 kernels).


This class of options tunes oclFFT performance
-oclfft_tune_gr N : Global radix
-oclfft_tune_lr N : Local radix
-oclfft_tune_wg N : Workgroup size
-oclfft_tune_ls N : Max size of local memory FFT
-oclfft_tune_bn N : Number of local memory banks
-oclfft_tune_cw N : Memory coalesce width

For examples of app_info.xml entries look into text file with .aistub extension provided in corresponding package.

Command line switches can be used either in app_info.xml or mb_cmdline.txt. Params in mb_cmdline*.txt will override switches in <cmdline> tag of app_info.xml.

For device-specific settings in multi-GPU systems it's possible to override some of command-line options via application config file.

Name of this config file:
MultiBeam_<vendor>_config.xml where vendor can be ATi, NV or iGPU.
File structure:
<deviceN>
	<period_iterations_num>N</period_iterations_num>
	<spike_fft_thresh>N</spike_fft_thresh>
	<sbs>N</sbs>
	<oclfft_plan>
	        <size>N</size>
		<global_radix>N</global_radix>
		<local_radix>N</local_radix>
		<workgroup_size>N</workgroup_size>
		<max_local_size>N</max_local_size>
		<localmem_banks>N</localmem_banks>
		<localmem_coalesce_width>N</localmem_coalesce_width>
	</oclfft_plan>
	<no_caching>
</deviceN>

where deviceN - particular OpenCL device N starting with 0, multiple sections allowed, one per each device.
other fields - corresponding command-line options to override for this particular device.
All or some sections can be omitted.

Don't forget to re-check device number to physical card relation after driver update and physical slot change. Both these actions can change cards enumeration order.

Best usage tips:
For best performance it is important to free 2 CPU cores running multiple instances. Freeing at least 1 CPU core is necessity to get enough GPU usage.

If you experience screen lags or driver restarts increase -period_iteration_num in app_info.xml or mb_cmdline*.txt
It is more important to free CPU core(s) so more instances are running.

============= ATi specific info ===============

Known issues:

- With 12.x Catalyst drivers GPU usage can be low if CPU fully used with another loads. App performance can be increased by using -cpu_lock switch in this case.

- Catalyst 12.11 beta and 13.1 have broken OpenCL compiler that will result in driver restarts or invalid results. But these drivers can be used still if the kernels binaries are precompiled under an older Catalyst driver. That is, delete all *.bin* files from SETI project directory, revert to Catalyst 12.8 or 12.10, or: upgrade to Catalyst 13.2 or later, process at least one task (check that those *.bin* files were generated again) and (if needed) update to Catalyst 13.1.
- New builds with versioned binary caches will require additional step: to rename old bin_* files to match name (driver version part of name) of newly generated ones.

App instances:

On high end cards HD 5850/5870, 6950/6970, 7950/7970, R9 280X/290X running 3 instances should be fastest.
HD 7950/7970 and R9 280X/290X can handle 4 instances very well. Testing required. Beware free CPU cores.

On mid range cards HD 5770, 6850/6870, 7850/7870 best performance should be running 2 instances.

Suggested command line switches:
_______________________________

Running 3 instances set -sbs 192 is best option for speed on 1GB GPU.
If only 2 instances are running set -sbs 256 for max speed up.
Users using GPU with 3 GB RAM set -sbs 244 - 280 for best speed also running 3 or more instances.
This might require some fine tuning.

One instance requires approx. 500 MB VRAM (depends on -sbs value used)

Entry level cards HD x3xx / x4xx R7 230/240/250
-spike_fft_thresh 2048 -tune 1 2 1 16

Mid range cards x5xx / x6xx / x7xx / R9 260 / 270
-spike_fft_thresh 2048 -tune 1 64 1 4

High end cards x8xx / x9xx / R9 280x / 290x
-spike_fft_thresh 4096 -tune 1 64 1 4 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 64 -oclfft_tune_cw 64


============= Intel specific info =============

Suggested command line switches:

HD 2500
-spike_fft_thresh 2048 -tune 1 2 1 16
(*requires testing)

HD 4000
-spike_fft_thresh 2048 -tune 1 64 1 4
(*requires testing)

HD 4200 / HD 4600 / HD 5xxx
-spike_fft_thresh 4096 -tune 1 64 1 4 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 512
(*requires testing)


============= NV specific info ================

Known issues:

With NV drivers past 267.xx GPU usage can be low if CPU fully used with another loads.
App performance can be increased by using -cpu_lock switch in this case, and CPU time savings are possible with -use_sleep switch.

Suggested command line switches:

Entry Level cards NV x20 x30 x40
-sbs 128 -spike_fft_thresh 2048 -tune 1 2 1 16
(*requires testing)

Mid range cards x50 x60 x70
-sbs 192 -spike_fft_thresh 2048 -tune 1 64 1 4
(*requires testing)

High end cards x8x 780TI Titan / Titan Z
-sbs 256 -spike_fft_thresh 4096 -tune 1 64 1 4 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 64 -oclfft_tune_cw 64
(*requires testing)

===============================================

FAQ:

To reduce screen lags especially running VLARs it is important to add
-period_iterations_num and -sbs value into mb_cmdline*.txt file.
Especially on slow GPUs you need to INCREASE -period_iterations_num to REDUCE screen lag.
Note each GPU has different characteristics so experimentation is required.

Example:
 -period_iterations_num  80 -sbs 128
 -period_iterations_num 100 -sbs 192
 -period_iterations_num 150 -sbs 256
 -period_iterations_num 200 -sbs 256

-period_iterations_num can be increased up to 1000 but this will significantly slow down processing.
This value increases wait loop between Pulse find Kernels.
-sbs value increases VRAM consumption but should also speed up computing.
26) Questions and Answers : Windows : ScreenSaver and Mouse Problem (Message 1847423)
Posted 17 days ago by Profile Ageless
Post:
Normally that's a setting in Windows. What you can try to do is:
Start->Search->type 'mouse' without quotes, wait for it to show in the search, click it.
In the window that opens, click Pointer Options->check "Show location of pointer when I press the CTRL key".

Also, make sure that the mouse doesn't go to sleep. Or that the port it's in is allowed by Windows to turn off to save power:
Start->search, type "management" and when populated, click "Computer Management". (all without quotes)
In the window that opens, click Device Manager.
In here find HID compliant mouse->right click on it->properties->Power management->uncheck "allow the computer to run off this device to save power"->OK.
If you have another mouse here, do the same for that - brand mice with their own drivers show both as HID compliant and as their own.
27) Message boards : Number crunching : PC Problem - Keeps shutting down (Message 1847338)
Posted 17 days ago by Profile Ageless
Post:
Check that your PSU (brand) doesn't show on Johnny Lucky PSU Lemon List or Newegg Eggxpert Tiered Power Supply List (old 2008 list). Even what you think is a good brand may not always be the case.

I can boot into CMOS and will run no problem (all last night 10 hours)
You can boot into BIOS. not into CMOS. The Complementary metal–oxide–semiconductor is a static RAM that can hold changes you made to the BIOS, but you cannot boot into it.
Also, booting into the BIOS will never take up as much power as booting into Windows will, as the latter will put load on a lot more of your hardware. Running work on one or more GPUs will then even put more load on the system, where an underpowered or on-the-way-of-going-broke PSU will cut out unexpectedly. And if your system is then not set up to reboot on situations like this, you'll find your PC shut down.

Over the past weeks, my monitors would flicker, cut out completely. I have two monitors connected to a single videocard.
When during playing Wolfenstein my whole system just shut down and rebooted, I knew that my PSU was on its last legs. And I found mine on the bad list, a Huntkey 600W - that I still don't know how I acquired it - so I have it replaced now with a Seasonic 620W. It even feels as if the whole system is faster, snappier.
28) Message boards : Number crunching : Panic Mode On (104) Server Problems? (Message 1847242)
Posted 18 days ago by Profile Ageless
Post:
Good. PSU is in, installed it.
1. Forgot the CPU cable, I can tell you the system won't boot then.
2. One of the SATA power cables wasn't plugged in right, so only the DVD was found.
But on the third try, everything started up... then windows told me that it had lost the hibernation file and that it had to boot normally and that everything that wasn't saved would go lost, would I like to continue? Like there's a choice... ;-)

Anyway, will now go back to testing.
29) Message boards : Number crunching : 725W for Four (4) RX 470 ATI Cards (Message 1847236)
Posted 18 days ago by Profile Ageless
Post:
I think that a 750W PSU will be at best "marginal" with four GPUs - I do note that XFX are somewhat reluctant to declare the power needs of these cards, so I would guess they are at the higher of the single 8-pin connector, say 150-175W each

I know, older post and all, but perhaps that someone wants to know. The XFX 470s draw 110W. (source 1, source 2)

Other brands on Alternate's websites show the same draw for the 470.
30) Message boards : Number crunching : Panic Mode On (104) Server Problems? (Message 1846861)
Posted 20 days ago by Profile Ageless
Post:
It's very slow around here, posting took 5 minutes to get through and then it did it twice. Panic!
31) Message boards : Number crunching : Panic Mode On (104) Server Problems? (Message 1846860)
Posted 20 days ago by Profile Ageless
Post:
I've ordered a Seasonic M12II-620W EVO, which is fully modular. Can even take the power cables off.
Was going for the Thermaltake up till I found that one, partly because you can control the fan speed via your mobile phone - really, I don't see the need either, but okay. :)
But also because it comes with a 7 year warranty.

Then I found Johnny Lucky PSU Lemon List in which some Thermaltakes aren't showing off as too well, and everywhere I look Seasonic is said to be the ultimate best in PSU. It being the same price as the beQuiet and the Thermaltake, I went for the Seasonic in the end.

All better than the Huntkey HK600-53AP server PSU I have in my case now - it came with my case and I must say I never checked up on it earlier, until my power outages happened. Apparently it's been in the tier 5 - or replace ASAP list of Newegg Eggxpert Tiered Power Supply List since 2008. Anything Huntkey in your system? Get rid of it pronto, as it can even damage your hardware.

So no more crunching for me until my Seasonic is in, no more gaming either. I'll be in the living room watching Fringe, or Knight Rider (TOS), or Andromeda. :)
Will have to wait until Tuesday afternoon for the new PSU to come in. Oooh, can't wait. :)
32) Message boards : Number crunching : Panic Mode On (104) Server Problems? (Message 1846736)
Posted 21 days ago by Profile Ageless
Post:
Well thank the deities for the breaks in work availability. My PSU is on its last legs, I'm seeing my monitors cut out a lot and have had two system power downs & reboots already. Still, gotta wait until Tuesday before my new PSU can come in (and so no need to order it until Monday - post deliveries, including packages aren't done here on Monday... only Tuesday -> Saturday)

Then I still have time to choose between the:
be quiet! Pure Power 10 600W CM, modular, protection: OCP, OVP, UVP, OLP/OPP, SCP and OTP, price € 94,90 + €4,95 shipping.
Cooler Master G650M, modular, protection: OCP, OVP, UVP, OLP/OPP, SCP and OTP, price € 82,90 with free shipping.
Thermaltake Smart DPS G 600W Bronze, modular, protection: OVP, OLP/OPP, SCP, price € 94,90 + €4,95 shipping.

No advice needed, I've got to make the choice. Am reading reviews now. :)
33) Questions and Answers : GPU applications : How to configure BONIC for NVIDIA GPU? (Message 1846623)
Posted 21 days ago by Profile Ageless
Post:
Each time that your BOINC connects to the project the server will send a delay for 5 minutes and 3 seconds before it allows a next communication from your BOINC. Hit Update inside this time and it'll tell you that you're too early and the timer resets to 5 minutes and 3 seconds (303 seconds).

04/02/2017 19:06:17 | SETI@home | Project requested delay of 303 seconds
04/02/2017 19:06:17 | SETI@home | [sched_op] Deferring communication for 00:05:03
This was done to stop lots of computers hitting the project over and over again and in that way creating a denial of service attack.

But as I said, any GPU usage decisions are only done via the Project Preferences, not via the (local) Computing Preferences. So again, setting a Suspend GPU when computer is in use preference will not affect the GPU asking for work, other than that it won't ask for work when there is work for it in cache, or when work for it is suspended due to the computer being in use.

I see you have enough work in cache now.
34) Questions and Answers : GPU applications : How to configure BONIC for NVIDIA GPU? (Message 1846481)
Posted 21 days ago by Profile Ageless
Post:
I tried to configure via XML export files.

Why do that difficult? I know some things about BOINC need simplification, but it's really not set up that people adding hardware that can be used for calculations need to learn BOINC XML to utilize it.

So, when you add a GPU, you need to tell the project that you have one and you do that via the project preferences.
You find these under your name in the top right corner of the forums->Preferences for this project->Edit preferences->Check Use NVIDIA GPU->Save changes to the web site via the Update preferences button at the bottom of that page.

Next tell BOINC that the project knows you're using an Nvidia GPU:
Simple view: Open BOINC Manager->Projects: from drop down menu select Seti@Home->Project commands button: click Update.
Advanced view: Open BOINC Manager->Projects tab->select Seti@Home from the list->click Update.

Manually editing coproc_info.xml will do nothing, as this file is written by BOINC each time it starts. Many of the XML files are written/rewritten by BOINC at startup, or during use. While manually editing cc_config.xml and changing <use_all_gpus> is nice, it won't make the project use the GPU if the project wasn't told in the first place that you have a GPU. Therefore: change this in the project preferences. And when you run more than one project, you need to do this per project in that project's project preferences as using the GPU isn't a global decision. Not all projects have applications that make use of an Nvidia GPU, or any GPU whatsoever.
35) Questions and Answers : Web site : Notice from BOINC (Message 1846013)
Posted 23 days ago by Profile Ageless
Post:
Make sure you see all tasks.
BOINC Manager->View->Advanced view->Tasks tab->if the button on the left says "Show all tasks" click it.
By default BOINC shows only the active tasks.

If that doesn't solve that, it's possible you have a lot of ghosts and yes the only thing you can do about that is let them time out.
36) Questions and Answers : Getting started : How does the statistics page work? (Message 1846003)
Posted 23 days ago by Profile Ageless
Post:
Recent Average Credit, I could go explain it in detail but someone already did that in this post. When left fully alone, it'll never reach zero again, but instead stay just above that at 0.07
The statistics boards are updated once every 24 hours, but credit in your account is updated as soon as it is granted.
37) Questions and Answers : Getting started : Dropped from my team - Founder issue (Message 1846000)
Posted 23 days ago by Profile Ageless
Post:
Sure, you can just not send PMs when:
1. not logged in.
2. banished.
3. perhaps with lacking a minimum amount of credit (not RAC).

But in all other cases, it should be possible to PM.
38) Questions and Answers : Getting started : Dropped from my team - Founder issue (Message 1845968)
Posted 23 days ago by Profile Ageless
Post:
You can do work as before, the credits you get for correct work are then just added to your account, not as well to the team.
You can also start your own team, if need be even with the same name.

Apropos, Seti started in 1999, you cannot have been a member of anything in 1998.
39) Questions and Answers : Unix/Linux : Making Boinc use identical boinc data folder on Windows and Linux (Ubuntu) (Message 1845859)
Posted 24 days ago by Profile Ageless
Post:
You cannot do that, because one of the two BOINC versions would then constantly overwrite the client_state.xml file with all the details of the host in it. The other host would then be detached.

You cannot run the same work on both hosts either, because Windows and Linux use different binaries.
Plus work for one hostID is registered to that hostID and that hostID must also report that work.

So no, not possible.
40) Questions and Answers : Web site : Missing ReCaptcha (Message 1845857)
Posted 24 days ago by Profile Ageless
Post:
Seeing that you're using Windows 10, are you sure you used Internet Explorer and not Edge?

I'll send a note to the developer of the forum software.


Previous 20 · Next 20


 
©2017 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.