Posts by Raistmer

1) Message boards : Number crunching : "BOINC portable" for Windows hosts (Message 1883347)
Posted 6 days ago by Profile Raistmer
Post:
P.S. and adding .exe to boinc in launching script helped with GPU detection too (at least on this netbook).
2) Message boards : Number crunching : "BOINC portable" for Windows hosts (Message 1883343)
Posted 6 days ago by Profile Raistmer
Post:
Try starting Manager from BOINCdata. I don't know what the --insecure really does.


This helped indeed, thanks! Now manager connected to daemon/client.
I checked registry - it has SSL entry with BOINC manager options. I assume it's inevitable registry pollution cause BOINC manager writes those options on each update (actually on each exit perhaps regardless real options update).
So, my attempt to run BOINC manager w/o client started still can be required step - will check by deleting registry entry.

EDIT: checked on another data directory with emptied registry - BOINC manager forgot about running in advanced mode, but connected to client with first attempt (being run from data directory instead of binary one).

So, the only real issues here:
1) lack of public info about such peculiarity (to launch from data dir)
2) misguided first error message.

Regarding 2 - still unsure why it changed from screenshot 1 to screenshot 2 after few attempts.
3) Message boards : Number crunching : "BOINC portable" for Windows hosts (Message 1883227)
Posted 7 days ago by Profile Raistmer
Post:

i.e. it isn't a Boinc or Manager problem, it is just the way that Windows ensures process security.

I'm quite sure that 2 processes can communicate being under same standard security context. So it's not Windows, it's BOINC attempting to run under some another user/security context instead of just accepting current context. W/o that attempt Windows security would not interfere at all.
4) Message boards : Number crunching : "BOINC portable" for Windows hosts (Message 1883201)
Posted 7 days ago by Profile Raistmer
Post:
For what function exactly BOINC manager needs elevated access or special security context?
As I see it all that needed is IPC between 2 processes running in the same security context.
Can't devise any sensible reason why it should be restricted.
It sounds if to as bug but as quite annoying and excessive "feature".
And if I will use BOINC tasks for example insyead of manager - will it connect? And if it will then this limitation of manager just ridiculous...
5) Message boards : Number crunching : "BOINC portable" for Windows hosts (Message 1883146)
Posted 7 days ago by Profile Raistmer
Post:
After netbook's HDD death and complete OS refreshment I copied old BOINC and BOINCdata folders to c:\ and attempting to configure "portable" variant to run w/o formal BOINC installation.

So I start daemon with bat file containing this line:
boinc.exe --dir ..\BOINCdata.old --skip_cpu_benchmarks --allow_remote_gui_rpc

and launch manager from command line:
boincmgr.exe /i

Despite using "insecure" option I got http://prntscr.com/g76rlp



What is wrong?

P.S. On first launch embedded Windows firewall asked permissions for BOINc - I allowed operation on both private and public networks.

P.P.S After few more attempts (run manager w/o deamon started and switched to advanced view) got such message: http://prntscr.com/g76xoj
But both started from C:\BOINC
6) Message boards : Number crunching : multi-client and GPU detection (Message 1880123)
Posted 24 days ago by Profile Raistmer
Post:
yes, that the way it works perfectly for CPU crunching also under linux; just create the data folder; standard manually the instances on different ports etc. Also starting the BM remotely with command parameter to reflect the different ports.

The only failing capability is the desired GPU detection when starting via simple separate data folders.

Based on Windows experience too, but for portable clients - analyse Juha's answer carefully - you need to run with full specified path, but not nessessarily different ones.
So you should go into BOINc dir and run multiple instances specifying different BOINC data dirs for each instance.
Each time you should use fully-specified path to BOINC executable (can be same one IMHO).
7) Message boards : Number crunching : New binary to test on beta (Message 1879973)
Posted 25 days ago by Profile Raistmer
Post:
x86 binary already built with enough level of optimization so not much sence to rebuild it.
Could try though but don't expect speedup.
8) Message boards : Number crunching : New binary to test on beta (Message 1879611)
Posted 27 days ago by Profile Raistmer
Post:
Yep. And could be online for month already :/
9) Message boards : Number crunching : "BOINC portable" for Windows hosts (Message 1876754)
Posted 4 Jul 2017 by Profile Raistmer
Post:
And on host with fully installed BOINC (with registry entries) no matter if I use boinc.exe --dir ... or boinc --dir... or just boinc w/o anything.
In all these cases BOINC client starts with correct directory and with GPU support.

So I still see inconsistency in observations on 2 different hosts (original one had full BOINC install also! Now on anoher host I see no issue with GPU detection no matter how I run boinc).

Difference in BOINC versions: current one is 7.6.9 vs recommended one (7.6.33) on original PC.
10) Message boards : Number crunching : Regular GPU or Mining-designed GPU (Message 1876686)
Posted 3 Jul 2017 by Profile Raistmer
Post:
Well, there was opinion that mining on GPU these days not cost the price of electricity it consumes.
That's why mining-specific ASICs were developed and sold for mining community.
Don't see the point of general purpose GPU rebranding then.
11) Message boards : Number crunching : Regular GPU or Mining-designed GPU (Message 1876600)
Posted 3 Jul 2017 by Profile Raistmer
Post:
Mining-specific is just as said - specific. That is, not general purpose.
12) Message boards : Number crunching : "BOINC portable" for Windows hosts (Message 1876578)
Posted 3 Jul 2017 by Profile Raistmer
Post:
Thanks all participants of this thread. I'm glad that this topic seemed interesting enough.
I'll continue experiments on another host soon.
13) Message boards : Number crunching : Regular GPU or Mining-designed GPU (Message 1876577)
Posted 3 Jul 2017 by Profile Raistmer
Post:
In past days grown in my mind this question. A GPU mining-designed would have better performance than a regular GPU?

This doubt is feeded by articles where says the some graphics chips are improved to get more efficiency with coin-mining's algorithm (maybe some BOINC-based projects will works better).

Thanks for read me. Cheers!

If you have enough money to buy ASIC development and production or can do that by yourself , then yes, ASIC-based SETI processing would be faster....
14) Message boards : Number crunching : "BOINC portable" for Windows hosts (Message 1876159)
Posted 1 Jul 2017 by Profile Raistmer
Post:
And back on topic:
I can't find (there is no) coproc_info on my computer (in fact no file with coproc in the name)
BOINC 6.10.58 is running now on:
https://setiathome.berkeley.edu/show_host_detail.php?hostid=4832843

So, you wanna say that usual setup with BOINC manager involved doesn't create tht file? This would fully explain my results indeed, but why such design decision???
15) Message boards : Number crunching : "BOINC portable" for Windows hosts (Message 1876158)
Posted 1 Jul 2017 by Profile Raistmer
Post:

There is no install, only small exe you run:
https://sourceforge.net/projects/swiftsearch/

whose purpose is to help you quickly find the files you need on your Windows machine without ever requiring you to index your drives

Given that embedded windows indexer slows down OS to such degree that really need to bother to disable it on each PC one really uses interactively, it's just another excellent piece of software found by you to add to collection. Thanks!

EDIT: BTW, if their claims are true it has another big implication. Hardly Windows OS routines SO worse than Unix ones. Still bypassing them in disk interations gives orders of magnitude speedup. And now recall David's attempts to use OS routines (!) for searching through SETI DB results and structures.... Surprise-surprise...
16) Message boards : Number crunching : Linux CUDA 'Special' App finally available, featuring Low CPU use (Message 1876144)
Posted 1 Jul 2017 by Profile Raistmer
Post:
Don't know, I found one of mine one count high against a CPU, https://setiathome.berkeley.edu/workunit.php?wuid=2588520990
My CPU says;
Spike count:    0
Autocorr count: 0
Pulse count:    10
Triplet count:  0
Gaussian count: 0

Perhaps there is still a little strangeness with the PulseFind...but it's rare.

And task re-run offline on GPU?
17) Message boards : Number crunching : "BOINC portable" for Windows hosts (Message 1876139)
Posted 1 Jul 2017 by Profile Raistmer
Post:
That all make a sense now, thanks for explanation.
But still it doesn't explain why I had issues with GPU detection on original host. If BOINC detect GPU in separate process then by the time of launching boinc.exe from command line it should have coproc_info.xml formed already. Cause that host crunched more than week with GPUs OK (under BOINC manager launched daemon).
Still it didn't detect GPU. Moreover, I did switch manager/command line few times - always under manager-launched client GPU tasks worked, under command line-launched client - didn't.
But I didn't launch boinc.exe with --detect_gpus on that host. But, if BOINC manager-launched client detects GPUs OK shouldn't it form coproc_info.xml ??
18) Message boards : Number crunching : "BOINC portable" for Windows hosts (Message 1875921)
Posted 30 Jun 2017 by Profile Raistmer
Post:

P:\bin\BOINC>boinc.exe --dir E:\BOINCdata --detect_gpus
Unknown option: --detect_gpus
Usage: P:\bin\BOINC\boinc.exe [options]
--help show options
--version show version info
--exit_when_idle exit when there are no results
--show_projects show attached projects
--return_results_immediately contact server when have results
--detach_project <URL> detach from a project
--reset_project <URL> reset (clear) a project
--attach_project <URL> <key> attach to a project
--update_prefs <URL> contact a project to update preferences
--run_cpu_benchmarks run the CPU benchmarks
--check_all_logins for idle detection, check remote logins too
--allow_remote_gui_rpc allow remote GUI RPC connections
--gui_rpc_port <port> port for GUI RPCs
--redirectio redirect stdout and stderr to log files
--detach detach from console (Windows)
--dir <path> use given dir as BOINC home
--no_gui_rpc don't allow GUI RPC, don't make socket
--daemon run as daemon (Unix)
--exit_before_start exit right before starting a job
--exit_after_finish exit right after finishing a job
--insecure disable app sandboxing (Unix)
--launched_by_manager core client was launched by Manager
--run_by_updater set by updater


Maybe it's available only in very recent versions? From what version?

More new one:
C:\Program Files\BOINC>boinc.exe --version
7.6.9 windows_x86_64

C:\Program Files\BOINC>boinc.exe --dir E:\BOINCdata\ --detect_gpus

That is, just immediately exits. W/o running daemon
19) Message boards : Number crunching : "BOINC portable" for Windows hosts (Message 1875880)
Posted 30 Jun 2017 by Profile Raistmer
Post:
On the offline boinc, did you try adding the --detectgpus flag when starting the client?

Not so far, thanks, will try.

Such flag undefined for boinc client I use (7.6.33 x64)


Sorry, the correct flag is: --detect_gpus

there is no such flags.
Where you found it?
20) Message boards : Number crunching : "BOINC portable" for Windows hosts (Message 1875879)
Posted 30 Jun 2017 by Profile Raistmer
Post:
BOINC.exe being started from command prompt doesn't detect GPUs

Try from elevated (admin) command prompt?

I can try just to rule that out but elevated privilegies not quite suitable for portable version in general.


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.