Welcome to MilkyWay@home

Posts by Vester

1) Message boards : Number crunching : Work Unit shortage (Message 70074)
Posted 21 days ago by ProfileVester
Post:
Check your PM regarding the procedure I use after I gleaned information from this topic.
2) Message boards : Number crunching : Twin CPUs and multi-core nbody tasks - success :-) (Message 70046)
Posted 26 days ago by ProfileVester
Post:
I run GPU only, but you may find what you need here to write an app_config.xml file.

App_config.xml is to be placed in C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway. To run 3 tasks with 8 cores each use notepad or other text editor and copy/paste a file such as:
<app_config>
<app>
<name>milkyway_nbody</name>
<max_concurrent>3</max_concurrent>
</app>
<app_version>
<app_name>milkyway_nbody</app_name>
<plan_class>mt</plan_class>
<cmdline>--nthreads 8</cmdline>
</app_version>
</app_config>
You will have to view hidden files to see Program Data. When written in notepad, it will appear as above, but you will need to "Save as... "app_config.xml" (without the quotes) and chose file File type *.* instead of .txt in the drop down.. To edit the .xml file, open it with Notepad by right-clicking on the file and selecting Edit.

This should get you started. I had waited hoping that a moderator or more experienced user would help you. Good luck.
3) Questions and Answers : Windows : General thinking about GPU computation (Message 69307)
Posted 26 Nov 2019 by ProfileVester
Post:
I am sorry that I am unable to help you, Diego. You can post this problem in the "Number crunching" forum. I have not seen a message in my app_config.xml file and I do not have any nVidia GPUs.
4) Questions and Answers : Windows : General thinking about GPU computation (Message 69300)
Posted 24 Nov 2019 by ProfileVester
Post:
One Euro is equal to 1.10 US dollars. I pay about 9.86 cents per kWh, or $0.0986. Round that number to $0.10 and I am still paying less than 0.10 EUR.

I am still trying to find the best number of work units per GPU and I am now running three per GPU.
5) Questions and Answers : Windows : General thinking about GPU computation (Message 69297)
Posted 24 Nov 2019 by ProfileVester
Post:
Three hundred seconds is for 7 WUs per GPU that I was running at that time, but remember that I have 6 GPUs, so the 300 should be divided by 7 (not 42) which gives a work unit time of 300 seconds divided by 7 work units = 42.857142857 seconds/work unit.
6) Questions and Answers : Windows : General thinking about GPU computation (Message 69290)
Posted 23 Nov 2019 by ProfileVester
Post:
I forgot to link to the sticky topic "Run Multiple WUs on Your GPU."
7) Questions and Answers : Windows : General thinking about GPU computation (Message 69288)
Posted 22 Nov 2019 by ProfileVester
Post:
I look some statistic of You Vester and also Jstateson. Looking the DP's abilities of yours GPU you should have more and more elaboration power in DP calculation than me.... But why both you two Vester and Jstateson take more time to complete works. What I missing? Do you share GPU time with more projects, dont' you use all the 100% of time of your GPU cards?
Many of us run more than one work unit per GPU by putting a file named app_config.xml in the milkyway.cs.rpi.edu_milkyway folder. I have six GPUs running 7 work units each. My information is shown in this image I posted for you on my Facebook page. When you look at the image, you can see that the folder I named is located on my Windows 10 computer at This PC > Local Disk (C) > Program Data > BOINC > Projects > milkyway.cs.rpi.edu_milkyway. If you do not see Program Data in your directory, you must show hidden files in File Folder Options on the View tab. To make app_config.xml you must use a text editor such as Notepad. For a four-core CPU and one GPU running four work units, one can run with:

<app_config>
<app>
<name>milkyway</name>
<gpu_versions>
<gpu_usage>0.25</gpu_usage>
<cpu_usage>1.0</cpu_usage>
</gpu_versions>
</app>
</app_config> 

On my computer, the gpu_usage value is 1/7 = 0.14 (rounded down from 0.142857143) and with the four-core processor (using six GPUs), I calculate cpu_usage as 4 divided by 42 (six GPUs multiplied by 7 WU each) = 0.095238095. I round down to the value 0.09.

Now that you have your app_config.txt file, you must save it as app_config.xml and be sure to use the drop-down selection "Save as type" "All Files."

The last thing to do is open the BOINC Manager and click on "Read config files" from the Options tab.
8) Questions and Answers : Windows : General thinking about GPU computation (Message 69277)
Posted 21 Nov 2019 by ProfileVester
Post:
Diego, here is an old table showing FP32 and FP64 performance for some video cards.

Don't go away, JStateson, I am trying to catch you. I have another HD 7990 on the way. I bought it on eBay for $189.99 and the seller claims that it is new. I will soon have four HD 7990s on my ASUS B250 Mining Expert rig. The four dual-GPU cards cost between $121 and $200 each.
9) Message boards : Number crunching : multithread (Message 68942)
Posted 1 Aug 2019 by ProfileVester
Post:
Yes, your CPU can be used. Go to https://milkyway.cs.rpi.edu/milkyway/home.php to set your preferences.
10) Message boards : Number crunching : Errors on de_modfit_14_bundle5_testing_ (runs) (Message 68941)
Posted 1 Aug 2019 by ProfileVester
Post:
I have been reluctant to post any errors because I have been sorting hardware problems which I believe have been rectified. This task and any others that I post shall have ended with an error on at least one other computer.
Task 280907267
Name de_modfit_14_bundle4_testing_3s4f_2_1564052102_1599249_1
Workunit 1786435876
Created 31 Jul 2019, 13:52:18 UTC
Sent 31 Jul 2019, 14:07:02 UTC
Report deadline 12 Aug 2019, 14:07:02 UTC
Received 31 Jul 2019, 15:16:10 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 1 (0x00000001) Unknown error code
Computer ID 808022
Run time 2 sec
CPU time
Validate state Invalid
Credit 0.00
Device peak FLOPS 823.78 GFLOPS
Application version Milkyway@home Separation v1.46 (opencl_ati_101)
windows_x86_64
Peak working set size 10.66 MB
Peak swap size 6.45 MB
Peak disk usage 0.01 MB
Stderr output

<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
Incorrect function.
(0x1) - exit code 1 (0x1)</message>
<stderr_txt>
<search_application> milkyway_separation 1.46 Windows x86 double OpenCL </search_application>
Reading preferences ended prematurely
BOINC GPU type suggests using OpenCL vendor 'Advanced Micro Devices, Inc.'
Parameter file 'astronomy_parameters.txt' is empty
Switching to Parameter File 'astronomy_parameters.txt'
Error reading number_parameters
11:08:25 (3068): called boinc_finish(1)

</stderr_txt>
]]>
11) Message boards : News : New Separation Runs [UPDATE] (Message 68935)
Posted 28 Jul 2019 by ProfileVester
Post:
Thank you. I hadn't had my cup of coffee yet. I thought the bugged units had been removed from the server(s) and did not read carefully.
12) Message boards : News : New Separation Runs [UPDATE] (Message 68933)
Posted 28 Jul 2019 by ProfileVester
Post:
I have had about three thousand work unit errors during a four hour period ending with the task quoted. A quick review found the errors to be mostly on de_modfit_85_bundle4_4s_south4s_bgset_2 and de_modfit_86_bundle4_4s_south4s_bgset_2. This is a typical error message:
Task 278472433
Name de_modfit_80_bundle4_4s_south4s_bgset_1561047003_12558111_2
Workunit 1784520616
Created 28 Jul 2019, 9:54:26 UTC
Sent 28 Jul 2019, 10:17:37 UTC
Report deadline 9 Aug 2019, 10:17:37 UTC
Received 28 Jul 2019, 11:14:41 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 1 (0x00000001) Unknown error code
Computer ID 808022
Run time 2 sec
CPU time
Validate state Invalid
Credit 0.00
Device peak FLOPS 823.78 GFLOPS
Application version Milkyway@home Separation v1.46 (opencl_ati_101)
windows_x86_64
Peak working set size 10.63 MB
Peak swap size 6.41 MB
Peak disk usage 0.01 MB
Stderr output

<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
Incorrect function.
(0x1) - exit code 1 (0x1)</message>
<stderr_txt>
<search_application> milkyway_separation 1.46 Windows x86 double OpenCL </search_application>
Reading preferences ended prematurely
BOINC GPU type suggests using OpenCL vendor 'Advanced Micro Devices, Inc.'
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4'
Switching to Parameter File 'astronomy_parameters.txt'
<number_WUs> 4 </number_WUs>
<number_params_per_WU> 25 </number_params_per_WU>
Number of streams does not match
07:13:15 (2824): called boinc_finish(1)

</stderr_txt>
]]>
13) Message boards : News : New Separation Runs [UPDATE] (Message 68929)
Posted 26 Jul 2019 by ProfileVester
Post:
I was away from home when you asked if I could clear the queue. The queue was empty when I returned and I updated to get new work. The new tasks are running without errors.
14) Message boards : News : New Separation Runs [UPDATE] (Message 68927)
Posted 26 Jul 2019 by ProfileVester
Post:
This is an example with full information. I have had about seven thousand errors.
Name de_modfit_85_bundle4_4s_south4s_bgset_1561047003_12568144_2
Workunit 1784531783
Created 26 Jul 2019, 1:35:00 UTC
Sent 26 Jul 2019, 2:01:22 UTC
Report deadline 7 Aug 2019, 2:01:22 UTC
Received 26 Jul 2019, 2:28:32 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 1 (0x00000001) Unknown error code
Computer ID 808022
Run time 1 sec
CPU time
Validate state Invalid
Credit 0.00
Device peak FLOPS 823.78 GFLOPS
Application version Milkyway@home Separation v1.46 (opencl_ati_101)
windows_x86_64
Peak disk usage 0.01 MB
Stderr output

<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
Incorrect function.
(0x1) - exit code 1 (0x1)</message>
<stderr_txt>
<search_application> milkyway_separation 1.46 Windows x86 double OpenCL </search_application>
Reading preferences ended prematurely
BOINC GPU type suggests using OpenCL vendor 'Advanced Micro Devices, Inc.'
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4'
Switching to Parameter File 'astronomy_parameters.txt'
<number_WUs> 4 </number_WUs>
<number_params_per_WU> 25 </number_params_per_WU>
Number of streams does not match
22:26:36 (1368): called boinc_finish(1)

</stderr_txt>
]]>
15) Message boards : News : New Separation Runs [UPDATE] (Message 68926)
Posted 26 Jul 2019 by ProfileVester
Post:
This is typical of thousands.
Stderr output

<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
Incorrect function.
(0x1) - exit code 1 (0x1)</message>
<stderr_txt>
<search_application> milkyway_separation 1.46 Windows x86 double OpenCL </search_application>
Reading preferences ended prematurely
BOINC GPU type suggests using OpenCL vendor 'Advanced Micro Devices, Inc.'
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4'
Switching to Parameter File 'astronomy_parameters.txt'
<number_WUs> 4 </number_WUs>
<number_params_per_WU> 25 </number_params_per_WU>
Number of streams does not match
22:26:36 (1368): called boinc_finish(1)

</stderr_txt>
]]>
16) Message boards : Number crunching : Computer details...wrong GPU description (Message 68888)
Posted 10 Jul 2019 by ProfileVester
Post:
I am running three video cards on computer ID 808022. The computer details list "[5] AMD AMD Radeon (TM) R9 390 Series (8192MB) OpenCL: 2.0" when I actually have one R9 390 and two dual GPU Radeon HD 7990s, which should be listed as "[4] AMD Radeon HD 7900 Series (3072MB) OpenCL: 1.2."

I wouldn't want anyone to purchase R9 390s for this project after they see my computer in the top computers listing.

The listing for the onboard Intel graphics is correct.
17) Message boards : News : New Separation Runs (Message 68812)
Posted 31 May 2019 by ProfileVester
Post:
This problem has been discussed in greater detail here: https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4434
It's an issue with the BOINC client as far as we know, what happens is that your computer won't automatically download more WU's until your job queue is complete, which can sometimes include validation of previous WU's. Sorry for the inconvenience, and know that we're looking into a solution for the future
.
It would be nice if the Event Log could say something other than the queue is full (when it is not full). I find it frustrating to tweak for this project and be denied work units because I am successful running sixteen WUs simultaneously on two AMD HD 7990s.
18) Message boards : Number crunching : There's something VERY wrong with the "Top GPU models" list (Message 66559)
Posted 10 Aug 2017 by ProfileVester
Post:
Is it possible for one to tell if a computer is running SLI or not?

SLI with two cards, per NVidia,
How much of a performance increase will I see with SLI technology?
The amount of performance improvement will depend on the application and its ability to scale. Several of today's hottest games see a full 2x increase in performance when using SLI technology with two graphics cards. 3-way NVIDIA SLI technology enables up to 2.8x performance increase over a single GPU. In general, applications running at higher resolutions with higher image quality settings will benefit most.


The GTX 560 specifications show that the GTX 560 Ti can be run in two-way SLI and the GTX 560 Ti Limited Edition can be run in three-way SLI.

This could explain the observed performance.
19) Message boards : Cafe MilkyWay : Quark soup is a Science dream of dangerous & cool! bios next ? (Message 66552)
Posted 3 Aug 2017 by ProfileVester
Post:
"Can't connect securely to this page." https://www.bnl.gov/newsroom/news.php?a=112068




©2020 Astroinformatics Group