Posts by Engagex

1) Message boards : Projects : SETI (Message 78767)
Posted 7 Jun 2017 by Engagex
Post:
On that same note could a BOINC app be developed to derive or read info from the IBM Q5 quantum computer? (to help facilitate the development of it). https://www.research.ibm.com/ibm-q/learn/

Since IBM already has a BOINC project: WCG, in theory it would be fairly easy to set up (permissions and access wise).
2) Message boards : GPUs : Multiple GPUs on same WU (Message 77525)
Posted 21 Apr 2017 by Engagex
Post:
Please continue thread here: http://moowrap.net/forum_thread.php?id=475&postid=7630#7630
3) Message boards : GPUs : Multiple GPUs on same WU (Message 76980)
Posted 28 Mar 2017 by Engagex
Post:
Yesterday (3/27/17) at 4:30 pm MST, I had this task that was ready to go: http://bit.ly/2mMFJT2

When I got in this morning (3/28/17) at 8:00 AM MST, it still hadn't ran.

I have my tasks set up to run for 60 minutes at a time.

I had to suspend all the running GPU tasks simultaneously for it to run.

It finished in 00:28:34.

Is there a priority scheduling problem with multiple GPUs on the same WU?
Seems like it would be the same as a Cosmology or other (4CPU or 6CPU task)

Please let me know any info you have.

Thanks, -Doug

P.S. How many Nvidia GPUs will be utilized simultaneously by a task like this?
I can have up to 7 cards on my MOBO.

Would 3 AMD cards work as well?

Could Nvidia and AMD be used on the same task?
4) Message boards : BOINC client : Assigning a CPU only project to less than 1 whole core (Message 76162)
Posted 26 Feb 2017 by Engagex
Post:
How would I go about specifying this setting in the config files?:
"Run CPU versions of applications for which GPU versions are available"

As I have computers on my grid that only crunch cpu tasks. Or would it be better all around to say no?

Also are CPU versions of apps any different than the GPU counterparts? Will the GPU versions return any additional data?
5) Message boards : BOINC client : Assigning a CPU only project to less than 1 whole core (Message 76119)
Posted 24 Feb 2017 by Engagex
Post:
Ok after actually reading the descriptions I just have one question left:

[<project_max_concurrent>N</project_max_concurrent>] (What's the difference between this and "<max_concurrent>7</max_concurrent>"?)
6) Message boards : BOINC client : Assigning a CPU only project to less than 1 whole core (Message 76118)
Posted 24 Feb 2017 by Engagex
Post:
Thank you for your prompt reply! I just have a few questions:

<app_config>
[<app> (My current config files do not have the brackets "[" is this necessary?)
<name>Application_Name</name>
<max_concurrent>1</max_concurrent>
[<fraction_done_exact/>] (This is a closing tag. Is there supposed to be an opening tag?)
<gpu_versions>
<gpu_usage>.5</gpu_usage>
<cpu_usage>.4</cpu_usage>
</gpu_versions>
</app>]
...
[<app_version>
<app_name>Application_Name</app_name>
[<plan_class>mt</plan_class>] (What variables replace "mt"?)
[<avg_ncpus>x</avg_ncpus>] (I can set this to ".X"?)
[<ngpus>x</ngpus>]
[<cmdline>--nthreads 7</cmdline>] (What's the difference between this and "<max_concurrent>7</max_concurrent>"?)
</app_version>]
...
[<project_max_concurrent>N</project_max_concurrent>] (What's the difference between this and "<max_concurrent>7</max_concurrent>"?)
</app_config>
7) Message boards : BOINC client : Assigning a CPU only project to less than 1 whole core (Message 76115)
Posted 24 Feb 2017 by Engagex
Post:
...app_config.xml - excuse me
8) Message boards : BOINC client : Assigning a CPU only project to less than 1 whole core (Message 76114)
Posted 24 Feb 2017 by Engagex
Post:
Is there a way to designate a CPU only project (i.e. Asteroids@Home) to only use a certain percentage of a cpu core (i.e. .1, .25, .5) rather than the core as a whole?

I've tried replacing <gpu_versions> in the app_config.conf with <cpu_versions> but it doesn't seem to be working.

If this feature doesn't have programming to support it please consider writing it. ;)



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.