Posts by ncoded.com

21) Message boards : Questions and problems : Running the same project twice (diff a/c's) within BOINC Manager? (Message 82672)
Posted 6 Nov 2017 by ncoded.com
Post:
I currently have different projects running in the BOINC Manager using different accounts and teams (grcpool.com and UK BOINC Team)

What I wanted to know is how the BOINC manager knows which account is being used; obviously it is in the project list as it shows username and team for each project

Is it just the BOINC manager that has this information, or is it also stored within the C:\ProgramData\BOINC\projects\ files (on Windows).

The reason that I ask is that I want to have Collatz added twice, one from UBT and one from GRC; however from what I can see there can only be one collatz project files - and hence I am trying to work out if this will work (eg the user/team is stored in the manager files) or if it will not (as the project files have this setting(s).

Can anyone shed any light on this?

Thanks
22) Message boards : The Lounge : Anyone using the Xeon E5-2696V4 / E5-2699V4 CPU? (Message 81575)
Posted 25 Sep 2017 by ncoded.com
Post:
In case anyone finds the following Xeon information useful!

V1/V0 Xeons



V3 Xeons



V4 Xeons



V5 Xeons

23) Message boards : The Lounge : Anyone using the Xeon E5-2696V4 / E5-2699V4 CPU? (Message 81574)
Posted 25 Sep 2017 by ncoded.com
Post:
Hi,

Is anyone using the Xeon E5-2696V4 / E5-2699V4 CPU?

(22 cores - 44 Threads - Base: 2.2 Ghz - Turbo: 3.8 Ghz - All cores: 2.8 Ghz - TDP 145/150w)

If so what kind of BOINC work are you getting out of it?

Is it running in a single or dual processor mobo?

Are you running a server/workstation mobo or a consumer X99 mobo?

Do you have any V3 CPUs running, and how does it compare to this/these?

If you have any V3 CPUs, are any E5-2683 V3 CPUs and if so how does it compare?

Thanks

Chris
24) Message boards : Questions and problems : GPU's listed in event manager log incl. "use all co-processors", but no (NVidia) GPU WUs being issued. (Gridcoin/GRCPool.com Manager) (Message 79499)
Posted 7 Jul 2017 by ncoded.com
Post:
Hi BobCat13,

I did try that with no joy. However, I just did the reverse, and un-checked every option, and now it has got NVidia GPU Tasks!?

To be honest I am not sure what is going on here. I have the GRC admin looking into this so hopefully he can shed some light on what is happening; it could well be with how I initially setup my account, rather than anything wrong with GRC specifically.

Thanks for your suggestion however.
25) Message boards : Questions and problems : GPU's listed in event manager log incl. "use all co-processors", but no (NVidia) GPU WUs being issued. (Gridcoin/GRCPool.com Manager) (Message 79492)
Posted 6 Jul 2017 by ncoded.com
Post:
Does this not indicate anything?

--

07/07/2017 00:07:34 | | [work_fetch] Request work fetch: Prefs update
07/07/2017 00:07:34 | | [work_fetch] Request work fetch: Startup
07/07/2017 00:07:34 | | [work_fetch] ------- start work fetch state -------
07/07/2017 00:07:34 | | [work_fetch] target work buffer: 8640.00 + 43200.00 sec
07/07/2017 00:07:34 | | [work_fetch] --- project states ---
07/07/2017 00:07:34 | Collatz Conjecture | [work_fetch] REC 291.266 prio -1.086 can request work
07/07/2017 00:07:34 | Einstein@Home | [work_fetch] REC 321.050 prio -1.197 can request work
07/07/2017 00:07:34 | World Community Grid | [work_fetch] REC 192.385 prio -0.727 can request work
07/07/2017 00:07:34 | | [work_fetch] --- state for CPU ---
07/07/2017 00:07:34 | | [work_fetch] shortfall 0.00 nidle 0.00 saturated 52064.01 busy 0.00
07/07/2017 00:07:34 | Collatz Conjecture | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:07:34 | Einstein@Home | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:07:34 | World Community Grid | [work_fetch] share 1.000
07/07/2017 00:07:34 | | [work_fetch] --- state for NVIDIA GPU ---
07/07/2017 00:07:34 | | [work_fetch] shortfall 103680.00 nidle 2.00 saturated 0.00 busy 0.00
07/07/2017 00:07:34 | Collatz Conjecture | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:07:34 | Einstein@Home | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:07:34 | World Community Grid | [work_fetch] share 0.000 blocked by project preferences
07/07/2017 00:07:34 | | [work_fetch] --- state for Intel GPU ---
07/07/2017 00:07:34 | | [work_fetch] shortfall 51840.00 nidle 1.00 saturated 0.00 busy 0.00
07/07/2017 00:07:34 | Collatz Conjecture | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:07:34 | Einstein@Home | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:07:34 | World Community Grid | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:07:34 | | [work_fetch] ------- end work fetch state -------
07/07/2017 00:07:34 | | [work_fetch] No project chosen for work fetch
07/07/2017 00:08:36 | | [work_fetch] ------- start work fetch state -------
07/07/2017 00:08:36 | | [work_fetch] target work buffer: 8640.00 + 43200.00 sec
07/07/2017 00:08:36 | | [work_fetch] --- project states ---
07/07/2017 00:08:36 | Collatz Conjecture | [work_fetch] REC 291.252 prio -1.085 can request work
07/07/2017 00:08:36 | Einstein@Home | [work_fetch] REC 321.034 prio -1.196 can request work
07/07/2017 00:08:36 | World Community Grid | [work_fetch] REC 192.707 prio -0.727 can request work
07/07/2017 00:08:36 | | [work_fetch] --- state for CPU ---
07/07/2017 00:08:36 | | [work_fetch] shortfall 0.00 nidle 0.00 saturated 51979.82 busy 0.00
07/07/2017 00:08:36 | Collatz Conjecture | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:08:36 | Einstein@Home | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:08:36 | World Community Grid | [work_fetch] share 1.000
07/07/2017 00:08:36 | | [work_fetch] --- state for NVIDIA GPU ---
07/07/2017 00:08:36 | | [work_fetch] shortfall 103680.00 nidle 2.00 saturated 0.00 busy 0.00
07/07/2017 00:08:36 | Collatz Conjecture | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:08:36 | Einstein@Home | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:08:36 | World Community Grid | [work_fetch] share 0.000 blocked by project preferences
07/07/2017 00:08:36 | | [work_fetch] --- state for Intel GPU ---
07/07/2017 00:08:36 | | [work_fetch] shortfall 51840.00 nidle 1.00 saturated 0.00 busy 0.00
07/07/2017 00:08:36 | Collatz Conjecture | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:08:36 | Einstein@Home | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:08:36 | World Community Grid | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:08:36 | | [work_fetch] ------- end work fetch state -------
07/07/2017 00:08:36 | | [work_fetch] No project chosen for work fetch
07/07/2017 00:09:36 | | [work_fetch] ------- start work fetch state -------
07/07/2017 00:09:36 | | [work_fetch] target work buffer: 8640.00 + 43200.00 sec
07/07/2017 00:09:36 | | [work_fetch] --- project states ---
07/07/2017 00:09:36 | Collatz Conjecture | [work_fetch] REC 291.238 prio -1.085 can request work
07/07/2017 00:09:36 | Einstein@Home | [work_fetch] REC 321.019 prio -1.196 can request work
07/07/2017 00:09:36 | World Community Grid | [work_fetch] REC 193.031 prio -0.728 can request work
07/07/2017 00:09:36 | | [work_fetch] --- state for CPU ---
07/07/2017 00:09:36 | | [work_fetch] shortfall 0.00 nidle 0.00 saturated 51915.03 busy 0.00
07/07/2017 00:09:36 | Collatz Conjecture | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:09:36 | Einstein@Home | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:09:36 | World Community Grid | [work_fetch] share 1.000
07/07/2017 00:09:36 | | [work_fetch] --- state for NVIDIA GPU ---
07/07/2017 00:09:36 | | [work_fetch] shortfall 103680.00 nidle 2.00 saturated 0.00 busy 0.00
07/07/2017 00:09:36 | Collatz Conjecture | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:09:36 | Einstein@Home | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:09:36 | World Community Grid | [work_fetch] share 0.000 blocked by project preferences
07/07/2017 00:09:36 | | [work_fetch] --- state for Intel GPU ---
07/07/2017 00:09:36 | | [work_fetch] shortfall 51840.00 nidle 1.00 saturated 0.00 busy 0.00
07/07/2017 00:09:36 | Collatz Conjecture | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:09:36 | Einstein@Home | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:09:36 | World Community Grid | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:09:36 | | [work_fetch] ------- end work fetch state -------
07/07/2017 00:09:36 | | [work_fetch] No project chosen for work fetch
26) Message boards : Questions and problems : GPU's listed in event manager log incl. "use all co-processors", but no (NVidia) GPU WUs being issued. (Gridcoin/GRCPool.com Manager) (Message 79491)
Posted 6 Jul 2017 by ncoded.com
Post:
What you see in that image is the *only options available in this 'account manager'. (grcpool.com)

What is strange is if I un-tick 'No Intel GPU' then straight away I get Intel GPU WUs, so GPUs must be enabled within the 'account manager'.

Just for some reason it is just not giving me NVidia WUs.

--

I noticed that within the BOINC manager that the following:

File | Activity | Use GPUs based on Preference

Was set, so I changed it to:

File | Activity | Use GPUs Always

Not that it made any difference.

--

I also suspended the CPU tasks to make sure this was not a 'High Priority Mode' issue, similar to what I had last time. But that did not change anything either.
27) Message boards : Questions and problems : GPU's listed in event manager log incl. "use all co-processors", but no (NVidia) GPU WUs being issued. (Gridcoin/GRCPool.com Manager) (Message 79488)
Posted 6 Jul 2017 by ncoded.com
Post:
Hi Ageless,

I have set the correct options at GRCPool.com (eg GridCoin).



I have also sent a message to the admin but I decided it may be posting in here in case I had missed anything with the event log.

Obviously Gridcoin and Collatz/Einstein are some of the largest projects/teams, and hence many people must be crunching using GTX970s in this pool on these projects, so I would be pretty surprised if it were a bug and not something local or account related.

--

Did you see the update that I did in that post - including a new listing of event manager log including debug information?

Does anyone, including yourself, notice anything that would cause this lack of GPU WUs in the log.

In truth it does not make much sense to us as it is quite BOINC-technical.

Thanks for your help so far.
28) Message boards : Questions and problems : GPU's listed in event manager log incl. "use all co-processors", but no (NVidia) GPU WUs being issued. (Gridcoin/GRCPool.com Manager) (Message 79486)
Posted 6 Jul 2017 by ncoded.com
Post:
Hi,

We have just setup a new install and Collatz and Einstein are refusing to issue GPU WUs.

Looking at the event manager log we noticed that GPU Cuda and GPU OpenCL are listed, but not GPU 0/GPU 1.

Also, there is no statement "No usable GPUs found".

However no GPUs (NVidia) are being issued WUs from Collatz or Einstein.

What what cause the GPUs not to be number listed (and hence usable)?

Thanks for any help on this.

Below is the full event manager log; as you can see with have set CC_config to use all co-processors, but have set No-intel-GPU WUs in each project. (via GRCPool.com)

--

06/07/2017 22:06:02 | | Starting BOINC client version 7.6.33 for windows_x86_64
06/07/2017 22:06:02 | | log flags: file_xfer, sched_ops, task
06/07/2017 22:06:02 | | Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8
06/07/2017 22:06:02 | | Data directory: C:\ProgramData\BOINC
06/07/2017 22:06:02 | | Running under account chris
06/07/2017 22:06:08 | | CUDA: NVIDIA GPU 0: GeForce GTX 970 (driver version 384.76, CUDA version 9.0, compute capability 5.2, 4096MB, 3389MB available, 4170 GFLOPS peak)
06/07/2017 22:06:08 | | CUDA: NVIDIA GPU 1: GeForce GTX 970 (driver version 384.76, CUDA version 9.0, compute capability 5.2, 4096MB, 3389MB available, 4423 GFLOPS peak)
06/07/2017 22:06:08 | | OpenCL: NVIDIA GPU 0: GeForce GTX 970 (driver version 384.76, device version OpenCL 1.2 CUDA, 4096MB, 3389MB available, 4170 GFLOPS peak)
06/07/2017 22:06:08 | | OpenCL: NVIDIA GPU 1: GeForce GTX 970 (driver version 384.76, device version OpenCL 1.2 CUDA, 4096MB, 3389MB available, 4423 GFLOPS peak)
06/07/2017 22:06:08 | | OpenCL: Intel GPU 0: Intel(R) HD Graphics 4600 (driver version 20.19.15.4531, device version OpenCL 1.2, 1630MB, 1630MB available, 192 GFLOPS peak)

06/07/2017 22:06:08 | | OpenCL CPU: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 5.2.0.10094, device version OpenCL 1.2 (Build 10094))
06/07/2017 22:06:08 | | Host name: i7-4790-2
06/07/2017 22:06:08 | | Processor: 8 GenuineIntel Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz [Family 6 Model 60 Stepping 3]
06/07/2017 22:06:08 | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 fma cx16 sse4_1 sse4_2 movebe popcnt aes f16c rdrandsyscall nx lm avx avx2 vmx smx tm2 pbe fsgsbase bmi1 smep bmi2
06/07/2017 22:06:08 | | OS: Microsoft Windows 10: Professional x64 Edition, (10.00.14393.00)
06/07/2017 22:06:08 | | Memory: 7.89 GB physical, 9.14 GB virtual
06/07/2017 22:06:08 | | Disk: 930.96 GB total, 881.71 GB free
06/07/2017 22:06:08 | | Local time is UTC +1 hours
06/07/2017 22:06:08 | | Config: use all coprocessors
06/07/2017 22:06:08 | Collatz Conjecture | URL https://boinc.thesonntags.com/collatz/; Computer ID 818506; resource share 100
06/07/2017 22:06:08 | Collatz Conjecture | Your current settings do not allow tasks from this project. To fix this, you can change your settings at your account manager web site.
06/07/2017 22:06:08 | Einstein@Home | URL http://einstein.phys.uwm.edu/; Computer ID 12545462; resource share 100
06/07/2017 22:06:08 | Einstein@Home | Your current settings do not allow tasks from this project. To fix this, you can change your settings at your account manager web site.
06/07/2017 22:06:08 | World Community Grid | URL http://www.worldcommunitygrid.org/; Computer ID 4024437; resource share 100
06/07/2017 22:06:09 | World Community Grid | General prefs: from World Community Grid (last modified 27-Jun-2017 14:59:47)
06/07/2017 22:06:09 | World Community Grid | Host location: none
06/07/2017 22:06:09 | World Community Grid | General prefs: using your defaults
06/07/2017 22:06:09 | | Reading preferences override file
06/07/2017 22:06:09 | | Preferences:
06/07/2017 22:06:09 | | max memory usage when active: 4037.24MB
06/07/2017 22:06:09 | | max memory usage when idle: 7267.03MB
06/07/2017 22:06:15 | | max disk usage: 837.86GB
06/07/2017 22:06:15 | | (to change preferences, visit a project web site or select Preferences in the Manager)

--

And this is the event log with some GPU/debug stuff turned on.

07/07/2017 00:07:33 | | Starting BOINC client version 7.6.33 for windows_x86_64
07/07/2017 00:07:33 | | log flags: file_xfer, sched_ops, task, coproc_debug, work_fetch_debug
07/07/2017 00:07:33 | | Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8
07/07/2017 00:07:33 | | Data directory: C:\ProgramData\BOINC
07/07/2017 00:07:33 | | Running under account chris
07/07/2017 00:07:33 | | [coproc] launching child process at C:\Program Files\BOINC\boinc.exe
07/07/2017 00:07:33 | | [coproc] relative to directory C:\ProgramData\BOINC
07/07/2017 00:07:33 | | [coproc] with data directory "C:\ProgramData\BOINC"
07/07/2017 00:07:34 | | CUDA: NVIDIA GPU 0: GeForce GTX 970 (driver version 384.76, CUDA version 9.0, compute capability 5.2, 4096MB, 3389MB available, 4170 GFLOPS peak)
07/07/2017 00:07:34 | | CUDA: NVIDIA GPU 1: GeForce GTX 970 (driver version 384.76, CUDA version 9.0, compute capability 5.2, 4096MB, 3389MB available, 4423 GFLOPS peak)
07/07/2017 00:07:34 | | OpenCL: NVIDIA GPU 0: GeForce GTX 970 (driver version 384.76, device version OpenCL 1.2 CUDA, 4096MB, 3389MB available, 4170 GFLOPS peak)
07/07/2017 00:07:34 | | OpenCL: NVIDIA GPU 1: GeForce GTX 970 (driver version 384.76, device version OpenCL 1.2 CUDA, 4096MB, 3389MB available, 4423 GFLOPS peak)
07/07/2017 00:07:34 | | OpenCL: Intel GPU 0: Intel(R) HD Graphics 4600 (driver version 20.19.15.4531, device version OpenCL 1.2, 1630MB, 1630MB available, 192 GFLOPS peak)
07/07/2017 00:07:34 | | OpenCL CPU: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 5.2.0.10094, device version OpenCL 1.2 (Build 10094))
07/07/2017 00:07:34 | | [coproc] NVIDIA library reports 2 GPUs
07/07/2017 00:07:34 | | [coproc] No ATI library found.
07/07/2017 00:07:34 | | Host name: i7-4790-2
07/07/2017 00:07:34 | | Processor: 8 GenuineIntel Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz [Family 6 Model 60 Stepping 3]
07/07/2017 00:07:34 | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 fma cx16 sse4_1 sse4_2 movebe popcnt aes f16c rdrandsyscall nx lm avx avx2 vmx smx tm2 pbe fsgsbase bmi1 smep bmi2
07/07/2017 00:07:34 | | OS: Microsoft Windows 10: Professional x64 Edition, (10.00.14393.00)
07/07/2017 00:07:34 | | Memory: 7.89 GB physical, 9.14 GB virtual
07/07/2017 00:07:34 | | Disk: 930.96 GB total, 882.09 GB free
07/07/2017 00:07:34 | | Local time is UTC +1 hours
07/07/2017 00:07:34 | | Config: use all coprocessors
07/07/2017 00:07:34 | Collatz Conjecture | URL https://boinc.thesonntags.com/collatz/; Computer ID 818506; resource share 100
07/07/2017 00:07:34 | Collatz Conjecture | Your current settings do not allow tasks from this project. To fix this, you can change your settings at your account manager web site.
07/07/2017 00:07:34 | Einstein@Home | URL http://einstein.phys.uwm.edu/; Computer ID 12545462; resource share 100
07/07/2017 00:07:34 | Einstein@Home | Your current settings do not allow tasks from this project. To fix this, you can change your settings at your account manager web site.
07/07/2017 00:07:34 | World Community Grid | URL http://www.worldcommunitygrid.org/; Computer ID 4024437; resource share 100
07/07/2017 00:07:34 | World Community Grid | General prefs: from World Community Grid (last modified 27-Jun-2017 14:59:47)
07/07/2017 00:07:34 | World Community Grid | Host location: none
07/07/2017 00:07:34 | World Community Grid | General prefs: using your defaults
07/07/2017 00:07:34 | | Reading preferences override file
07/07/2017 00:07:34 | | Preferences:
07/07/2017 00:07:34 | | max memory usage when active: 4037.24MB
07/07/2017 00:07:34 | | max memory usage when idle: 7267.03MB
07/07/2017 00:07:34 | | max disk usage: 837.86GB
07/07/2017 00:07:34 | | (to change preferences, visit a project web site or select Preferences in the Manager)
07/07/2017 00:07:34 | | [work_fetch] Request work fetch: Prefs update
07/07/2017 00:07:34 | | [work_fetch] Request work fetch: Startup
07/07/2017 00:07:34 | | [work_fetch] ------- start work fetch state -------
07/07/2017 00:07:34 | | [work_fetch] target work buffer: 8640.00 + 43200.00 sec
07/07/2017 00:07:34 | | [work_fetch] --- project states ---
07/07/2017 00:07:34 | Collatz Conjecture | [work_fetch] REC 291.266 prio -1.086 can request work
07/07/2017 00:07:34 | Einstein@Home | [work_fetch] REC 321.050 prio -1.197 can request work
07/07/2017 00:07:34 | World Community Grid | [work_fetch] REC 192.385 prio -0.727 can request work
07/07/2017 00:07:34 | | [work_fetch] --- state for CPU ---
07/07/2017 00:07:34 | | [work_fetch] shortfall 0.00 nidle 0.00 saturated 52064.01 busy 0.00
07/07/2017 00:07:34 | Collatz Conjecture | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:07:34 | Einstein@Home | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:07:34 | World Community Grid | [work_fetch] share 1.000
07/07/2017 00:07:34 | | [work_fetch] --- state for NVIDIA GPU ---
07/07/2017 00:07:34 | | [work_fetch] shortfall 103680.00 nidle 2.00 saturated 0.00 busy 0.00
07/07/2017 00:07:34 | Collatz Conjecture | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:07:34 | Einstein@Home | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:07:34 | World Community Grid | [work_fetch] share 0.000 blocked by project preferences
07/07/2017 00:07:34 | | [work_fetch] --- state for Intel GPU ---
07/07/2017 00:07:34 | | [work_fetch] shortfall 51840.00 nidle 1.00 saturated 0.00 busy 0.00
07/07/2017 00:07:34 | Collatz Conjecture | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:07:34 | Einstein@Home | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:07:34 | World Community Grid | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:07:34 | | [work_fetch] ------- end work fetch state -------
07/07/2017 00:07:34 | | [work_fetch] No project chosen for work fetch
07/07/2017 00:08:36 | | [work_fetch] ------- start work fetch state -------
07/07/2017 00:08:36 | | [work_fetch] target work buffer: 8640.00 + 43200.00 sec
07/07/2017 00:08:36 | | [work_fetch] --- project states ---
07/07/2017 00:08:36 | Collatz Conjecture | [work_fetch] REC 291.252 prio -1.085 can request work
07/07/2017 00:08:36 | Einstein@Home | [work_fetch] REC 321.034 prio -1.196 can request work
07/07/2017 00:08:36 | World Community Grid | [work_fetch] REC 192.707 prio -0.727 can request work
07/07/2017 00:08:36 | | [work_fetch] --- state for CPU ---
07/07/2017 00:08:36 | | [work_fetch] shortfall 0.00 nidle 0.00 saturated 51979.82 busy 0.00
07/07/2017 00:08:36 | Collatz Conjecture | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:08:36 | Einstein@Home | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:08:36 | World Community Grid | [work_fetch] share 1.000
07/07/2017 00:08:36 | | [work_fetch] --- state for NVIDIA GPU ---
07/07/2017 00:08:36 | | [work_fetch] shortfall 103680.00 nidle 2.00 saturated 0.00 busy 0.00
07/07/2017 00:08:36 | Collatz Conjecture | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:08:36 | Einstein@Home | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:08:36 | World Community Grid | [work_fetch] share 0.000 blocked by project preferences
07/07/2017 00:08:36 | | [work_fetch] --- state for Intel GPU ---
07/07/2017 00:08:36 | | [work_fetch] shortfall 51840.00 nidle 1.00 saturated 0.00 busy 0.00
07/07/2017 00:08:36 | Collatz Conjecture | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:08:36 | Einstein@Home | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:08:36 | World Community Grid | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:08:36 | | [work_fetch] ------- end work fetch state -------
07/07/2017 00:08:36 | | [work_fetch] No project chosen for work fetch
07/07/2017 00:09:36 | | [work_fetch] ------- start work fetch state -------
07/07/2017 00:09:36 | | [work_fetch] target work buffer: 8640.00 + 43200.00 sec
07/07/2017 00:09:36 | | [work_fetch] --- project states ---
07/07/2017 00:09:36 | Collatz Conjecture | [work_fetch] REC 291.238 prio -1.085 can request work
07/07/2017 00:09:36 | Einstein@Home | [work_fetch] REC 321.019 prio -1.196 can request work
07/07/2017 00:09:36 | World Community Grid | [work_fetch] REC 193.031 prio -0.728 can request work
07/07/2017 00:09:36 | | [work_fetch] --- state for CPU ---
07/07/2017 00:09:36 | | [work_fetch] shortfall 0.00 nidle 0.00 saturated 51915.03 busy 0.00
07/07/2017 00:09:36 | Collatz Conjecture | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:09:36 | Einstein@Home | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:09:36 | World Community Grid | [work_fetch] share 1.000
07/07/2017 00:09:36 | | [work_fetch] --- state for NVIDIA GPU ---
07/07/2017 00:09:36 | | [work_fetch] shortfall 103680.00 nidle 2.00 saturated 0.00 busy 0.00
07/07/2017 00:09:36 | Collatz Conjecture | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:09:36 | Einstein@Home | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:09:36 | World Community Grid | [work_fetch] share 0.000 blocked by project preferences
07/07/2017 00:09:36 | | [work_fetch] --- state for Intel GPU ---
07/07/2017 00:09:36 | | [work_fetch] shortfall 51840.00 nidle 1.00 saturated 0.00 busy 0.00
07/07/2017 00:09:36 | Collatz Conjecture | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:09:36 | Einstein@Home | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:09:36 | World Community Grid | [work_fetch] share 0.000 account manager prefs
07/07/2017 00:09:36 | | [work_fetch] ------- end work fetch state -------
07/07/2017 00:09:36 | | [work_fetch] No project chosen for work fetch
29) Message boards : Questions and problems : Location of Event Log (file)? (Message 79485)
Posted 6 Jul 2017 by ncoded.com
Post:
Thank you Agentb, that is very useful.

Sorry I have only just seen this post.
30) Message boards : Questions and problems : Location of Event Log (file)? (Message 78362)
Posted 29 May 2017 by ncoded.com
Post:
Would it be possible to make a suggestion?

Could I suggest that this file be written out as a CSV file? If would be a lot easier to read in code if the file were.

The reason I ask is because if you try and import this file it basically breaks the whole file apart and makes it unusable, as it gets confused between the space used as a delimiter within the first 2 elements, and then the later spaces within the description; eg uploaded XXXXX etc.

Thanks
31) Message boards : Questions and problems : Location of Event Log (file)? (Message 78360)
Posted 29 May 2017 by ncoded.com
Post:
Thank you Ageless, its much appreciated.
32) Message boards : Questions and problems : Location of Event Log (file)? (Message 78358)
Posted 29 May 2017 by ncoded.com
Post:
Hi,

We have done a search on Event log file location and nothing came up hence why we post this question.

Can someone tell us where the information presented in:

Tools | Event Log

Is actually stored, and if it is within a file, or some other persistent storage?

We want to write some software that analyses Work Units (WU) that have been downloaded and reported with 24 hours, and this would seem the best way to do this as it contains the necessary information within the Event Log.

Obviously we would be mindful of the file being possibly locked due to the BOINC client reading/writing into it.

Thanks.
33) Message boards : Questions and problems : ** Solved ** Retrieving donations made to each project, via code/XML files? (Message 77505)
Posted 20 Apr 2017 by ncoded.com
Post:
Hi ChristianB,

Thanks for the update; I have only just seen your message.

To be honest it is not essential and I am sure the BOINC developers have 101 other things of more importance; I can just keep a list of donations.

I agree, scraping this off page's is not really a very good solution, for many reasons, one which you have given.

Thanks for the information.
34) Message boards : Questions and problems : Top 100 not been updated since Jan? (Message 77365)
Posted 13 Apr 2017 by ncoded.com
Post:
Thank you Ageless.
35) Message boards : Questions and problems : Top 100 not been updated since Jan? (Message 77358)
Posted 13 Apr 2017 by ncoded.com
Post:
Hi,

Can we ask when the Top 100 will next be updated?

For a while we thought it was updating quite regular.

Thanks
36) Message boards : GPUs : How to exclude multiple GPUs for a given Project, using GPU_Exclude ? (Message 76752)
Posted 24 Mar 2017 by ncoded.com
Post:
Sorry you lost me a little bit there :?

When we move in/out all the GPUs I shall just take a look at the Event log to find out which GPU is numbered which.

In terms of the IGPU, because we are using a Xeon CPU it means there is no on-board IGPU.

To be honest we stopped using the IGPUs on our i7s as it seemed to overheat the CPUs when running at 100% load for weeks whilst using using stock Intel coolers.

At the moment we are just testing out the new GTX 1080 on this motherboard hence why we only have 2 NVIdia GPUs in place; in the next day or so though I am going to move this motherboard into the GPURack and then hook up probably 4 GPUs.

After months of research we went with a X99 LGA-2011 V3 motherboard due to as explained below..

--

In terms of the GPU Rack, just to explain, and in-case anyone is interesting in how we set it up and what we used:

We went with ASUS X99 Deluxe motherboard + Xeon E5-2683 V3 CPU (28 cores) as it is perfect for a GPU Rack.

The X99 Deluxe can:

    Take V3 Xeon CPUs, which have 40 PCIE lanes
    Has 4 PCIE slots (x16 size) at Gen3 with speeds (x16,x8,x8,x8) or 5 PCIE slots (x16 size) at Gen3 with speeds (x8.x8.x8.x8,x8)
    Can "overclock" (full Turbo) the CPU just by clicking a button in the BIOS (OCGenie); make sure you pick the correct RAM speed for the Xeon.
    Has an ATX Form Factor size which fits the GPU Rack
    Takes DDR4 RAM which is obviously much better than DDR3



To make sure we keep the full x16/x8 speed we are using x16 to x16 (molex powered) PCIE risers so that we get the full x16 data bus from motherboard to GPU.

** Note - The PCIE slots above, at those speeds, are only available for Xeons, due to the 40 PCIE lanes, not i7's etc which only have 16 PCIE lanes. **

** Note - The X99 Deluxe actually has 6 GPU slots, however if you use all them then you would not get the PCIE speeds as given above, which may or many not have relevance dependent on which project you crunch as well as what GPU(s) you use.

--

If I get a chance I will take a photo of the GPU Rack once is built in a day or so, and post it as it looks quite good :)

37) Message boards : GPUs : How to exclude multiple GPUs for a given Project, using GPU_Exclude ? (Message 76749)
Posted 24 Mar 2017 by ncoded.com
Post:
We only use NVidia GPUs, and always turn off Intel IGPUs across all projects, so its less of an issue for us.
it won't hurt to specify the GPU brand


What a I would say on the GPU numbeing. is on some mobos/gpus it is different; which is why I guess you said *usually.
In our case, the current setup is:

    ASUS X99-Deluxe Motherboard (LGA 2011-V3)
    GPUs are a MSI 1080 and a Asus 970.



The 970 is in slot 1, and the 1080 is in slot 2. However the event log shows that the 1080 is GPU 0, and the 970 is GPU 1.
That is why I noted that it is probably best to check the Event Log to see exactly which number each GPU has been allocated.

Anyway, thanks for all the help and information, its much appreciated.

38) Message boards : GPUs : How to exclude multiple GPUs for a given Project, using GPU_Exclude ? (Message 76736)
Posted 24 Mar 2017 by ncoded.com
Post:
Where is the edit button for my last post?

(Remembering of course that GPUs are numbered from zero, not one; and as you stated that each brand: NVidia/ATI/Intel has their own number list)


This is wrong..

GPUs are numbered according to:

Tools/Event Log - from the top menu within the BOINC client.
39) Message boards : GPUs : How to exclude multiple GPUs for a given Project, using GPU_Exclude ? (Message 76733)
Posted 24 Mar 2017 by ncoded.com
Post:
Hi Jord, Richard.

Thanks for the information.

I was not sure where the manual was located so it good that I now have this.

http://boinc.berkeley.edu/wiki/Client_configuration#Options

Although I would agree that the entry it is a little unclear it respects to different GPU brands, and having to put in multiple <exclude_gpus>, one for each device when excluding multiple GPUs; Perhaps another two examples showing these variants would be useful. (as given below).

--

So just to confirm, for myself, and others..

I would use (a) to use the 1st GPU for GPUGrid, but exclude the remaining 3 GPUs, however also have all GPUs used for every other project?

And, use (b) to do the same, but in the case where the first 2 GPUs were NVidia, and the remaining 2 GPUs were ATI?

(Remembering of course that GPUs are numbered from zero, not one; and as you stated that each brand: NVidia/ATI/Intel has their own number list)

(a)

<cc_config>
<options>
<use_all_gpus>1</use_all_gpus>

<exclude_gpu>
<url>www.gpugrid.net</url>
<device_num>1</device_num>
</exclude_gpu>

<exclude_gpu>
<url>www.gpugrid.net</url>
<device_num>2</device_num>
</exclude_gpu>

<exclude_gpu>
<url>www.gpugrid.net</url>
<device_num>3</device_num>
</exclude_gpu>

</options>
</cc_config>

(b)

<cc_config>
<options>
<use_all_gpus>1</use_all_gpus>

<exclude_gpu>
<url>www.gpugrid.net</url>
<device_num>1</device_num>
<type>NVIDIA</type>
</exclude_gpu>

<exclude_gpu>
<url>www.gpugrid.net</url>
<device_num>0-</device_num>
<type>ATI</type>
</exclude_gpu>

<exclude_gpu>
<url>www.gpugrid.net</url>
<device_num>1</device_num>
<type>ATI</type>
</exclude_gpu>

</options>
</cc_config>

--

Just as a side issue, just so you know, when subscribed to a thread, such as this one, no notification of new posts are being sent.
40) Message boards : GPUs : How to exclude multiple GPUs for a given Project, using GPU_Exclude ? (Message 76720)
Posted 23 Mar 2017 by ncoded.com
Post:
Hi,

I have this, to use the first GPU but exclude the 2nd for a given project, but use all GPUs for the rest of the projects.

<cc_config>
<options>
<use_all_gpus>1</use_all_gpus>
<exclude_gpu>
<url>www.gpugrid.net</url>
<device_num>1</device_num>
<type>NVIDIA</type>
</exclude_gpu>
</options>
</cc_config>

However, I am about to move all 4/5 GPUs into our GPURack and therefore I was wondering how I would exclude say 3/4 GPUs from a given Project? I am guessing it would something like:

<device_num>1,2,3,4</device_num>

or

<device_num>1</device_num>
<device_num>2</device_num>
..
..

Could someone advise; I have done a search but cannot find anything related to excluding more than one GPU within a single system.

Thanks.


Previous 20 · Next 20

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.