Posts by Jorge Ramos

1) Message boards : Questions and problems : GPU Work Units Only (Message 47100)
Posted 7 Jan 2013 by Jorge Ramos
Post:
<ncpus>0</ncpus> is a debug setting, David has said before that it shouldn't be used to limit the number of CPU cores in use, we have the 'On multiprocessors, use at most x processors' and the 'On multiprocessors, use at most 100% of the processors' settings for that,


Another example in "multiplicity" of configuration parameters.


+1

And they wonder why people are confused by BOINC. They think the more options the better and they ignore the fact that every time they provide an option they force the user to make a decision. When users are running software for charity they don't have motivation to spend time and effort making a lot of decisions unless the option is well documented and they don't have to look very far to find the documentation. They want it all done, installed and ready to go in 10 clicks or less. Anything more is an annoyance to them.

Responses to this line of reasoning will begin with "well if you don't like it go make your own BOINC". If we persist after that we will be banished so be careful what you say.


Personal disclaimer: ;)

As a volunteer tester, I really appreciate the work done by BOINC programmers. I do not expect perfection from BOINC and I guess some programmers are or have some kind of volunteering in their work too. I know, by personal experience, that you cannot build a system and expect everyone would be happy with it.

I am not a scientist but try to support science in any way I can. Having said that, everything is perfectible and I feel I might add to construction of this great endeavour by giving my opinion, in the light of an average-joe user.

Just as I can sometimes ask for help in these forums, I feel obligated to give one's back in return whenever I can.

Every bit of ideas I might post here are just my 2 cents for improving the useability of BOINC from the point of view of an average user, imho. Whether someone would find this usefull or not, is not for me to decide, but that is not reason enough for me to restrain me from expressing anything which actually did diminish my experience with the use of the software.

No personal offense is meant to anyone in this and all threads I might post. ;)
2) Message boards : Questions and problems : Conflicting titles for project configuration (Message 47093)
Posted 7 Jan 2013 by Jorge Ramos
Post:
As BOINC is the common platform for both SETI and GPUGrid, I posted here, but should I be posting this anywhere other place?
3) Message boards : Questions and problems : Conflicting titles for project configuration (Message 47091)
Posted 7 Jan 2013 by Jorge Ramos
Post:
I have SETI and GPUGrid for projects. When selecting the "computing preferences" in each project, yields two different titles under the "Network usage" section. SETI reports as:

"Maintain enough tasks to keep busy for at least
(max 10 days).
"

while GPUGrid reports:

"Computer is connected to the Internet about every
Leave blank or 0 if always connected.
"

both will affect the same parameter but, obviously, they do not mean the same thing. I am having trouble configuring my client for GPU usage (posted in another thread) and debugging it becomes obscure when the 2 projects I am involved give different meanings to the same parameter.
4) Message boards : Questions and problems : GPU Work Units Only (Message 47090)
Posted 7 Jan 2013 by Jorge Ramos
Post:
<ncpus>0</ncpus> is a debug setting, David has said before that it shouldn't be used to limit the number of CPU cores in use, we have the 'On multiprocessors, use at most x processors' and the 'On multiprocessors, use at most 100% of the processors' settings for that,


Another example in "multiplicity" of configuration parameters.
5) Message boards : Questions and problems : GPU Work Units Only (Message 47084)
Posted 6 Jan 2013 by Jorge Ramos
Post:
The error seems to be with <ncpus>0</ncpus>
I am getting GPU units just fine, but I'm still getting CPU units.


Use the project preferences to set "use CPU" to No and whichever GPU(s) you have to Yes.


This may cause confusion to some of us. Although the <ncpus> is also used to simulate "multicore" cpus, but it also has the 0-parameter, which according to the wiki page: "in newer clients really means zero to e.g. only allow GPU computing"

I have placed 0 to <ncpus> in my config file (as I don't want to use cpu for computing) but also have set the "use CPU" option to "no" in my computing preferences in the project's website.

It works, but I guess this can be done more user friendly and would be wiser to discourage the use of duplicate functions in configuration parameters.
6) Message boards : Questions and problems : 7.0.25 Doesn't fetch work when cc_config excludes GPU's (Message 46995)
Posted 1 Jan 2013 by Jorge Ramos
Post:
The bug here is that you're still expecting BOINC 7.0 to work like previous BOINC versions did, where it will fetch work for whatever project e.g. when it's just uploaded & reported work for that project. Sort of to top off the cache all the time.

BOINC 7.0 does not work this way. It will only fetch work when the total work cache is below that of the minimum work buffer value and then it will only fetch work from the project with the highest priority (priority == 0, or close to it, like -0.05), and only if that project does not have work, will it fetch work from the next, and the next, etc.


Found this thread to be related to a problem I have. Runnig BOINC 7.0.28, win7 x64, 2 projects: GPUGrid and SETI@Home, "5" GPUs: two GTX 690s ("4" GTX 680s) and 1 GT 640. Here is my config file:

<cc_config>

	<options>

		<use_all_gpus>1</use_all_gpus>

		<ncpus>0</ncpus>

		<report_results_immediately>1</report_results_immediately>

		<exclude_gpu>
			<url>http://www.gpugrid.net/</url>
				[<device_num>1</device_num>]
		</exclude_gpu>

		<exclude_gpu>
			<url>http://setiathome.berkeley.edu/</url>
				[<device_num>0</device_num>]
		</exclude_gpu>
		<exclude_gpu>
			<url>http://setiathome.berkeley.edu/</url>
				[<device_num>2</device_num>]
		</exclude_gpu>
		<exclude_gpu>
			<url>http://setiathome.berkeley.edu/</url>
				[<device_num>3</device_num>]
		</exclude_gpu>
		<exclude_gpu>
			<url>http://setiathome.berkeley.edu/</url>
				[<device_num>4</device_num>]
		</exclude_gpu>

		<max_file_xfers_per_project>4</max_file_xfers_per_project>

	</options>

</cc_config>


Which means I am using the GT 640 (device 1) for SETI@Home and the two GTX 690s (devices 0, 2, 3 and 4) for GPUGrid. The problem is:

GPUGrid gets a full workload (the 4 devices are working with one workunit each) for about a day or so. The next day GPUGrid only crunches 2 workunits, thus leaving the other 2 devices sitting idle. This cycle repeats itself indefinitely.

I would love to know a workaround for this issue. I am not running 2 different instances of BOINC, but would consider doing so if it is the only way for crunching at all times my GTX 690s. I have set a project resource share 50-50 (that is, 100 each).

Any ideas?
7) Message boards : Questions and problems : GPU Work Units Only (Message 46990)
Posted 1 Jan 2013 by Jorge Ramos
Post:
Try configuring your client:

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

1st step is ok:

<ncpus>0</ncpus>


you may also have to:

<use_all_gpus>1</use_all_gpus>


look, what device number your card is, as viewed from the client (check the log file, you should see something like:)

30/12/2012 11:44:24 p.m. |  | Disk: 465.76 GB total, 440.65 GB free
30/12/2012 11:44:24 p.m. |  | Local time is UTC -6 hours
[b]30/12/2012 11:44:24 p.m. |  | NVIDIA GPU 0: GeForce GTX 690 (driver version 310.70, CUDA version 5.0, compute capability 3.0, 2048MB, 8382371MB available, 3132 GFLOPS peak)[/b]


In this example the 690 is device 0. If you have several devices (GPUs) listed there you should restrict use of your 9400 using the flag

<exclude_gpu>
8) Message boards : Questions and problems : New client, new dirver, new NVIDIA GPU problem (Message 32123)
Posted 11 Apr 2010 by Jorge Ramos
Post:
The strange thing is that BOINC reports less memory but everywhere else in the computer (system information, NVIDIA control panel, etc) video memory is reported correctly (256 MB). Why does BOINC report less memory?
9) Message boards : Questions and problems : New client, new dirver, new NVIDIA GPU problem (Message 32094)
Posted 11 Apr 2010 by Jorge Ramos
Post:
I forgot to post my preferences...

10/04/2010 11:36:54 p.m. Starting BOINC client version 6.10.43 for windows_x86_64
10/04/2010 11:36:54 p.m. log flags: file_xfer, sched_ops, task
10/04/2010 11:36:54 p.m. Libraries: libcurl/7.19.7 OpenSSL/0.9.8l zlib/1.2.3
10/04/2010 11:36:54 p.m. Data directory: C:\ProgramData\BOINC
10/04/2010 11:36:54 p.m. Running under account Jorge
10/04/2010 11:36:54 p.m. Processor: 2 GenuineIntel Intel(R) Core(TM)2 Duo CPU P7350 @ 2.00GHz [Family 6 Model 23 Stepping 10]
10/04/2010 11:36:54 p.m. Processor: 3.00 MB cache
10/04/2010 11:36:54 p.m. 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 cx16 sse4_1 syscall nx lm tm2 pbe
10/04/2010 11:36:54 p.m. OS: Microsoft Windows Vista: Home Premium x64 Edition, Service Pack 2, (06.00.6002.00)
10/04/2010 11:36:54 p.m. Memory: 3.75 GB physical, 8.52 GB virtual
10/04/2010 11:36:54 p.m. Disk: 262.99 GB total, 203.57 GB free
10/04/2010 11:36:54 p.m. Local time is UTC -5 hours
10/04/2010 11:36:54 p.m. NVIDIA GPU 0: GeForce 9500M (GF 9200MGS + GF 9400MG) (driver version 19716, CUDA version 3000, compute capability 1.1, 240MB, 21 GFLOPS peak)
10/04/2010 11:36:55 p.m. SETI@home URL http://setiathome.berkeley.edu/; Computer ID 5366766; resource share 100
10/04/2010 11:36:55 p.m. No general preferences found - using BOINC defaults
10/04/2010 11:36:55 p.m. Preferences:
10/04/2010 11:36:55 p.m. max memory usage when active: 1918.71MB
10/04/2010 11:36:55 p.m. max memory usage when idle: 3453.69MB
10/04/2010 11:36:55 p.m. max disk usage: 10.00GB
10/04/2010 11:36:55 p.m. don't use GPU while active
10/04/2010 11:36:55 p.m. suspend work if non-BOINC CPU load exceeds 25 %
10/04/2010 11:36:55 p.m. (to change, visit the web site of an attached project,
10/04/2010 11:36:55 p.m. or click on Preferences)
10/04/2010 11:36:57 p.m. Using proxy info from GUI
10/04/2010 11:36:57 p.m. Not using a proxy
10) Message boards : Questions and problems : New client, new dirver, new NVIDIA GPU problem (Message 32093)
Posted 11 Apr 2010 by Jorge Ramos
Post:
Hi all, this is my input:

10/04/2010 11:54:28 p.m. SETI@home update requested by user
10/04/2010 11:54:33 p.m. SETI@home Sending scheduler request: Requested by user.
10/04/2010 11:54:33 p.m. SETI@home Requesting new tasks for GPU
10/04/2010 11:54:38 p.m. SETI@home Scheduler request completed: got 0 new tasks
10/04/2010 11:54:38 p.m. SETI@home Message from server: (Project has no jobs available)
10/04/2010 11:54:53 p.m. SETI@home Sending scheduler request: To fetch work.
10/04/2010 11:54:53 p.m. SETI@home Requesting new tasks for GPU
10/04/2010 11:54:58 p.m. SETI@home Scheduler request completed: got 0 new tasks
10/04/2010 11:54:58 p.m. SETI@home Message from server: (Project has no jobs available)
10/04/2010 11:55:13 p.m. SETI@home Sending scheduler request: To fetch work.
10/04/2010 11:55:13 p.m. SETI@home Requesting new tasks for GPU
10/04/2010 11:55:18 p.m. SETI@home Scheduler request completed: got 0 new tasks
10/04/2010 11:55:18 p.m. SETI@home Message from server: (Project has no jobs available)
10/04/2010 11:56:33 p.m. SETI@home Sending scheduler request: To fetch work.
10/04/2010 11:56:33 p.m. SETI@home Requesting new tasks for GPU
10/04/2010 11:56:38 p.m. SETI@home Scheduler request completed: got 0 new tasks
10/04/2010 11:56:38 p.m. SETI@home Message from server: No work sent
10/04/2010 11:56:38 p.m. SETI@home Message from server: Your NVIDIA GPU has insufficient memory (need 254MB)
10/04/2010 11:56:38 p.m. SETI@home Message from server: Your NVIDIA GPU has insufficient memory (need 384MB)
11/04/2010 12:00:25 a.m. Suspending computation - CPU usage is too high
11/04/2010 12:00:35 a.m. Resuming computation
11/04/2010 12:02:39 a.m. SETI@home Sending scheduler request: To fetch work.
11/04/2010 12:02:39 a.m. SETI@home Requesting new tasks for GPU
11/04/2010 12:02:44 a.m. SETI@home Scheduler request completed: got 0 new tasks
11/04/2010 12:02:44 a.m. SETI@home Message from server: (Project has no jobs available)

Earlier I had the previous version of BOINC and a previous version of NVIDIA driver (I think it was 186.85) I am now running Vista 64 (I also had Win 7 64 with no problems at all) and I have a 256MB card (NVIDIA GeForce 9500M (GF 9200MGS + GF 9400MG running in hybrid SLI)) with driver version 197.16. I had the GPU working before, I don't know if it is the client, or the new driver, but the servers now respond that the GPU has insuficient memory? and at other times that the server has no jobs available? I'm confused... any ideas?

thanks.
11) Message boards : Questions and problems : What does 0.01 CPUs mean? (Message 27710)
Posted 1 Oct 2009 by Jorge Ramos
Post:
In CUDA tasks?

thanks,

Jorge
12) Message boards : Questions and problems : BOINC CUDA Device recognizing problem (Message 27225)
Posted 9 Sep 2009 by Jorge Ramos
Post:
Hi:

I think I know what the problem is... Because my PC is a Laptop and it has a hybrid-SLI system, there exists the posibility that when I rebooted the PC, the energy savings protocol was active, and the discrete GPU (which is the one responsible for CUDA in my system) was inactive a the time when BOINC started automatically and tried to detect a cuda device (which I think it does scan the system after every reboot).

I havn't been able to test this, mainly because I am full of workload now (CPU and GPU) and havn't restarted my PC since.
13) Message boards : Questions and problems : BOINC CUDA Device recognizing problem (Message 27111)
Posted 6 Sep 2009 by Jorge Ramos
Post:
Maybe this problem could be solved if, BOINC don't erase (CUDA) computing data if suddenly, it canĀ“t recognize a CUDA device in the system, when it was working fine prior a reboot or a shut-down.

The work done so far can be recalled after another reboot or shutdown, when BOINC would recognize the CUDA device.
14) Message boards : Questions and problems : BOINC CUDA Device recognizing problem (Message 27076)
Posted 5 Sep 2009 by Jorge Ramos
Post:
Hi:

The Dell XPS 1340 has the option of the "9500M GPU", not the original one, but a combination of the mGPU 9400M + a discrete 9200M GS GPU working in Hybrid-SLI mode, thus creating a boost in performance when the two are active (which is this case). This is much like the case of the MAcbook Pro which are now available with the 9400M mGPU + a discrete 9600M GPU.


Jorge.
15) Message boards : Questions and problems : BOINC CUDA Device recognizing problem (Message 27074)
Posted 5 Sep 2009 by Jorge Ramos
Post:
Hi:

Yes... it's a Dell Studio XPS 1340

Jorge.
16) Message boards : Questions and problems : BOINC CUDA Device recognizing problem (Message 27062)
Posted 4 Sep 2009 by Jorge Ramos
Post:
Yesterday I installed the newest version of BOINC in to my PC that is running Windows Vista 64 bit edition (service pack 2). I have an NVIDIA CUDA capable GPU, and when first installed, BOINC recognized the GPU inmediatly (im using the latest drivers from NVIDIA 186.81), downloaded a workunit for the GPU (as well for the CPUs) and started computation normally.

There is a problem when I restart or shut down the PC: when the client restarts at boot, there are sometimes when the client doesn't recognize a CUDA device in the system, therefore loosing all data computed before. I don't know exactly why this happens as there are other tmes when the PC is restarted or rebooted and there are no problems at all.

This has happen at least thrice the last day, and now the server won't give me any other GPU workunits. The GPU never had a chance to compute an entire workunit because of this problem. Here are the latest messages from the client: (this time, after a reboot when the client didn't recognize a CUDA device, now recognized it)

04/09/2009 08:53:14 a.m. Starting BOINC client version 6.6.36 for windows_x86_64
04/09/2009 08:53:14 a.m. log flags: task, file_xfer, sched_ops
04/09/2009 08:53:14 a.m. Libraries: libcurl/7.19.4 OpenSSL/0.9.8j zlib/1.2.3
04/09/2009 08:53:14 a.m. Data directory: C:\ProgramData\BOINC
04/09/2009 08:53:14 a.m. Running under account Jorge Ramos
04/09/2009 08:53:14 a.m. Processor: 2 GenuineIntel Intel(R) Core(TM)2 Duo CPU P7350 @ 2.00GHz [Intel64 Family 6 Model 23 Stepping 10]
04/09/2009 08:53:14 a.m. Processor features: fpu tsc pae nx sse sse2 pni
04/09/2009 08:53:14 a.m. OS: Microsoft Windows Vista: Home Premium x64 Edition, Service Pack 2, (06.00.6002.00)
04/09/2009 08:53:14 a.m. Memory: 3.75 GB physical, 3.63 GB virtual
04/09/2009 08:53:14 a.m. Disk: 282.99 GB total, 227.62 GB free
04/09/2009 08:53:14 a.m. Local time is UTC -5 hours
04/09/2009 08:53:14 a.m. CUDA device: GeForce 9500M (GF 9200MGS + GF 9400MG) (driver version 18681, compute capability 1.1, 256MB, est. 4GFLOPS)
04/09/2009 08:53:14 a.m. Not using a proxy
04/09/2009 08:53:14 a.m. SETI@home URL: http://setiathome.berkeley.edu/; Computer ID: 5093139; location: (none); project prefs: default
04/09/2009 08:53:14 a.m. No general preferences found - using BOINC defaults
04/09/2009 08:53:14 a.m. Reading preferences override file
04/09/2009 08:53:14 a.m. Preferences limit memory usage when active to 1918.71MB
04/09/2009 08:53:14 a.m. Preferences limit memory usage when idle to 3453.69MB
04/09/2009 08:53:14 a.m. Preferences limit disk usage to 10.00GB
04/09/2009 08:53:14 a.m. SETI@home Restarting task ap_23ap08ab_B3_P1_00107_20090903_28463.wu_0 using astropulse_v505 version 505
04/09/2009 08:53:14 a.m. SETI@home Restarting task ap_23au08ae_B5_P0_00353_20090901_11107.wu_2 using astropulse_v505 version 505
04/09/2009 08:53:14 a.m. SETI@home Sending scheduler request: To fetch work.
04/09/2009 08:53:14 a.m. SETI@home Requesting new tasks for GPU
04/09/2009 08:53:28 a.m. SETI@home Scheduler request completed: got 0 new tasks
04/09/2009 08:53:28 a.m. SETI@home Message from server: (Project has no jobs available)
04/09/2009 08:54:44 a.m. SETI@home Sending scheduler request: To fetch work.
04/09/2009 08:54:44 a.m. SETI@home Requesting new tasks for GPU
04/09/2009 08:54:50 a.m. SETI@home Scheduler request completed: got 0 new tasks
04/09/2009 08:54:50 a.m. SETI@home Message from server: (Project has no jobs available)
04/09/2009 08:56:06 a.m. SETI@home Sending scheduler request: To fetch work.
04/09/2009 08:56:06 a.m. SETI@home Requesting new tasks for GPU
04/09/2009 08:56:11 a.m. SETI@home Scheduler request completed: got 0 new tasks
04/09/2009 08:56:11 a.m. SETI@home Message from server: (Project has no jobs available)
04/09/2009 08:57:27 a.m. SETI@home Sending scheduler request: To fetch work.
04/09/2009 08:57:27 a.m. SETI@home Requesting new tasks for GPU
04/09/2009 08:57:32 a.m. SETI@home Scheduler request completed: got 0 new tasks
04/09/2009 08:57:32 a.m. SETI@home Message from server: (Project has no jobs available)
04/09/2009 08:58:48 a.m. SETI@home Sending scheduler request: To fetch work.
04/09/2009 08:58:48 a.m. SETI@home Requesting new tasks for GPU
04/09/2009 08:58:53 a.m. SETI@home Scheduler request completed: got 0 new tasks
04/09/2009 08:58:53 a.m. SETI@home Message from server: (Project has no jobs available)
04/09/2009 09:05:14 a.m. SETI@home Sending scheduler request: To fetch work.
04/09/2009 09:05:14 a.m. SETI@home Requesting new tasks for GPU
04/09/2009 09:05:19 a.m. SETI@home Scheduler request completed: got 0 new tasks
04/09/2009 09:05:19 a.m. SETI@home Message from server: (Project has no jobs available)
04/09/2009 09:32:38 a.m. SETI@home Sending scheduler request: To fetch work.
04/09/2009 09:32:38 a.m. SETI@home Requesting new tasks for GPU
04/09/2009 09:32:43 a.m. SETI@home Scheduler request completed: got 0 new tasks
04/09/2009 09:32:43 a.m. SETI@home Message from server: (Project has no jobs available)
04/09/2009 09:34:58 a.m. SETI@home Sending scheduler request: To fetch work.
04/09/2009 09:34:58 a.m. SETI@home Requesting new tasks for GPU
04/09/2009 09:35:03 a.m. SETI@home Scheduler request completed: got 0 new tasks
04/09/2009 09:35:03 a.m. SETI@home Message from server: (Project has no jobs available)


This problem only happens with the GPU, the CPUs are working just fine. any help is appreciated.




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.