Posts by X-Files 27


log in
1) Message boards : Number crunching : Error -11 (0xfffffffffffffff5) (Message 1309036)
Posted 612 days ago by Profile X-Files 27
Your appinfo has some errors.

First of all the copy tag is missing in the r390 section.
Evenso ffa_block, ffa_block_fetch and unroll are astropulse params not MB one so beeing ignored.



The copyfile works, Thanks!
2) Message boards : Number crunching : Error -11 (0xfffffffffffffff5) (Message 1308608)
Posted 613 days ago by Profile X-Files 27
How do i fix this? I'm new to ATI crunching.

Running SetiPerformance_32_64_1_4__OpenCL_ATI_NV_Added-by-BilBg completes successfully.

Link to one of the error: 2721067135

<app_info>
<app>
<name>astropulse_v6</name>
<user_friendly_name>S@H AP r1316 CL</user_friendly_name>
</app>
<file_info>
<name>astropulse_6.04_windows_intelx86__opencl_ati_100.exe</name>
<executable/>
</file_info>
<file_info>
<name>astropulse_6.04_windows_intelx86__opencl_ati_100.pdb</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>AstroPulse_Kernels_r1316.cl</name>
<executable/>
</file_info>
<file_info>
<name>ap_cmdline_6.04_windows_intelx86__opencl_ati.txt</name>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.10</avg_ncpus>
<max_ncpus>0.10</max_ncpus>
<flops>1087928871804.144300</flops>
<plan_class>opencl_ati_100</plan_class>
<cmdline>-ffa_block 6144 -ffa_block_fetch 1536 -unroll 10 -instances_per_device 3 -hp</cmdline>
<coproc>
<type>ATI</type>
<count>.33</count>
</coproc>
<file_ref>
<file_name>astropulse_6.04_windows_intelx86__opencl_ati_100.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>astropulse_6.04_windows_intelx86__opencl_ati_100.pdb</file_name>
<open_name>astropulse_6.04_windows_intelx86__opencl_ati_100.pdb</open_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
<open_name>libfftw3f-3.dll</open_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1316.cl</file_name>
<open_name>AstroPulse_Kernels_r1316.cl</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>ap_cmdline_6.04_windows_intelx86__opencl_ati.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.10</avg_ncpus>
<max_ncpus>0.10</max_ncpus>
<flops>1087928871804.144300</flops>
<plan_class>ati_opencl_100</plan_class>
<cmdline>-ffa_block 6144 -ffa_block_fetch 1536 -unroll 10 -instances_per_device 3 -hp</cmdline>
<coproc>
<type>ATI</type>
<count>.33</count>
</coproc>
<file_ref>
<file_name>astropulse_6.04_windows_intelx86__opencl_ati_100.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>astropulse_6.04_windows_intelx86__opencl_ati_100.pdb</file_name>
<open_name>astropulse_6.04_windows_intelx86__opencl_ati_100.pdb</open_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
<open_name>libfftw3f-3.dll</open_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1316.cl</file_name>
<open_name>AstroPulse_Kernels_r1316.cl</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>ap_cmdline_6.04_windows_intelx86__opencl_ati.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>

<app>
<name>setiathome_enhanced</name>
<user_friendly_name>S@H MB r390 CL</user_friendly_name>
</app>
<file_info>
<name>MB6_win_x86_SSE3_OpenCL_ATi_HD5_r390.exe</name>
<executable/>
</file_info>
<file_info>
<name>MultiBeam_Kernels_r390.cl</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.10</avg_ncpus>
<max_ncpus>0.10</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline>-period_iterations_num 20 -ffa_block 6144 -ffa_block_fetch 1536 -unroll 10 -instances_per_device 3 -hp</cmdline>
<coproc>
<type>ATI</type>
<count>.33</count>
</coproc>
<file_ref>
<file_name>MB6_win_x86_SSE3_OpenCL_ATi_HD5_r390.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r390.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.10</avg_ncpus>
<max_ncpus>0.10</max_ncpus>
<plan_class>ati_opencl_100</plan_class>
<cmdline>-period_iterations_num 20 -ffa_block 6144 -ffa_block_fetch 1536 -unroll 10 -instances_per_device 3 -hp</cmdline>
<coproc>
<type>ATI</type>
<count>.33</count>
</coproc>
<file_ref>
<file_name>MB6_win_x86_SSE3_OpenCL_ATi_HD5_r390.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r390.cl</file_name>
</file_ref>
</app_version>
</app_info>
3) Message boards : Number crunching : Optimize your GPU. Find the value the easy way. (Message 1284146)
Posted 680 days ago by Profile X-Files 27
Using: 306.23
GPU0: 580 @833/1004/1666
GPU1: 580 @815/1004/1630
GPU2: 570 @810/975/1620

Starting automatic test: (x41g) Workunit: PG0395_v7.wu
15 September 2012 - 10:49:41 Start, devices: 3, device count: 1 (1.00) (Wu: PG0395_v7.wu)
--------------------------------------------------------------------------- Results: (PG0395_v7.wu)
Device: 0, device count: 1, average time / count: 32, average time on device: 32 Seconds (0 Minutes, 32 Seconds)
Device: 1, device count: 1, average time / count: 33, average time on device: 33 Seconds (0 Minutes, 33 Seconds)
Device: 2, device count: 1, average time / count: 36, average time on device: 36 Seconds (0 Minutes, 36 Seconds)
Next :---------------------------------------------------------------------------
15 September 2012 - 10:50:19 Start, devices: 3, device count: 2 (0.50) (Wu: PG0395_v7.wu)
--------------------------------------------------------------------------- Results: (PG0395_v7.wu)
Device: 0, device count: 2, average time / count: 50, average time on device: 25 Seconds (0 Minutes, 25 Seconds)
Device: 1, device count: 2, average time / count: 50, average time on device: 25 Seconds (0 Minutes, 25 Seconds)
Device: 2, device count: 2, average time / count: 58, average time on device: 29 Seconds (0 Minutes, 29 Seconds)
Next :---------------------------------------------------------------------------
15 September 2012 - 10:51:20 Start, devices: 3, device count: 3 (0.33) (Wu: PG0395_v7.wu)
--------------------------------------------------------------------------- Results: (PG0395_v7.wu)
Device: 0, device count: 3, average time / count: 74, average time on device: 24 Seconds (0 Minutes, 24 Seconds)
Device: 1, device count: 3, average time / count: 72, average time on device: 24 Seconds (0 Minutes, 24 Seconds)
Device: 2, device count: 3, average time / count: 84, average time on device: 28 Seconds (0 Minutes, 28 Seconds)
Next :---------------------------------------------------------------------------
15 September 2012 - 10:52:46 Start, devices: 3, device count: 4 (0.25) (Wu: PG0395_v7.wu)
--------------------------------------------------------------------------- Results: (PG0395_v7.wu)
Device: 0, device count: 4, average time / count: 96, average time on device: 24 Seconds (0 Minutes, 24 Seconds)
Device: 1, device count: 4, average time / count: 95, average time on device: 23 Seconds (0 Minutes, 23 Seconds)
Device: 2, device count: 4, average time / count: 110, average time on device: 27 Seconds (0 Minutes, 27 Seconds)
>> The best average time found: 25 Seconds (0 Minutes, 25 Seconds), with count: 0.33 (3)
--------------------------------------------------------------------------- Next
15 September 2012 - 10:54:41 Start, devices: 3, device count: 1 (1.00) (Wu: PG0444_v7.wu)
--------------------------------------------------------------------------- Results: (PG0444_v7.wu)
Device: 0, device count: 1, average time / count: 31, average time on device: 31 Seconds (0 Minutes, 31 Seconds)
Device: 1, device count: 1, average time / count: 32, average time on device: 32 Seconds (0 Minutes, 32 Seconds)
Device: 2, device count: 1, average time / count: 35, average time on device: 35 Seconds (0 Minutes, 35 Seconds)
Next :---------------------------------------------------------------------------
15 September 2012 - 10:55:19 Start, devices: 3, device count: 2 (0.50) (Wu: PG0444_v7.wu)
--------------------------------------------------------------------------- Results: (PG0444_v7.wu)
Device: 0, device count: 2, average time / count: 49, average time on device: 24 Seconds (0 Minutes, 24 Seconds)
Device: 1, device count: 2, average time / count: 49, average time on device: 24 Seconds (0 Minutes, 24 Seconds)
Device: 2, device count: 2, average time / count: 56, average time on device: 28 Seconds (0 Minutes, 28 Seconds)
Next :---------------------------------------------------------------------------
15 September 2012 - 10:56:18 Start, devices: 3, device count: 3 (0.33) (Wu: PG0444_v7.wu)
--------------------------------------------------------------------------- Results: (PG0444_v7.wu)
Device: 0, device count: 3, average time / count: 70, average time on device: 23 Seconds (0 Minutes, 23 Seconds)
Device: 1, device count: 3, average time / count: 71, average time on device: 23 Seconds (0 Minutes, 23 Seconds)
Device: 2, device count: 3, average time / count: 80, average time on device: 26 Seconds (0 Minutes, 26 Seconds)
Next :---------------------------------------------------------------------------
15 September 2012 - 10:57:40 Start, devices: 3, device count: 4 (0.25) (Wu: PG0444_v7.wu)
--------------------------------------------------------------------------- Results: (PG0444_v7.wu)
Device: 0, device count: 4, average time / count: 94, average time on device: 23 Seconds (0 Minutes, 23 Seconds)
Device: 1, device count: 4, average time / count: 93, average time on device: 23 Seconds (0 Minutes, 23 Seconds)
Device: 2, device count: 4, average time / count: 106, average time on device: 26 Seconds (0 Minutes, 26 Seconds)
>> The best average time found: 24 Seconds (0 Minutes, 24 Seconds), with count: 0.33 (3)
--------------------------------------------------------------------------- Next
15 September 2012 - 10:59:29 Start, devices: 3, device count: 1 (1.00) (Wu: PG1327_v7.wu)
--------------------------------------------------------------------------- Results: (PG1327_v7.wu)
Device: 0, device count: 1, average time / count: 41, average time on device: 41 Seconds (0 Minutes, 41 Seconds)
Device: 1, device count: 1, average time / count: 42, average time on device: 42 Seconds (0 Minutes, 42 Seconds)
Device: 2, device count: 1, average time / count: 45, average time on device: 45 Seconds (0 Minutes, 45 Seconds)
Next :---------------------------------------------------------------------------
15 September 2012 - 11:00:17 Start, devices: 3, device count: 2 (0.50) (Wu: PG1327_v7.wu)
--------------------------------------------------------------------------- Results: (PG1327_v7.wu)
Device: 0, device count: 2, average time / count: 56, average time on device: 28 Seconds (0 Minutes, 28 Seconds)
Device: 1, device count: 2, average time / count: 56, average time on device: 28 Seconds (0 Minutes, 28 Seconds)
Device: 2, device count: 2, average time / count: 65, average time on device: 32 Seconds (0 Minutes, 32 Seconds)
Next :---------------------------------------------------------------------------
15 September 2012 - 11:01:23 Start, devices: 3, device count: 3 (0.33) (Wu: PG1327_v7.wu)
--------------------------------------------------------------------------- Results: (PG1327_v7.wu)
Device: 0, device count: 3, average time / count: 82, average time on device: 27 Seconds (0 Minutes, 27 Seconds)
Device: 1, device count: 3, average time / count: 81, average time on device: 27 Seconds (0 Minutes, 27 Seconds)
Device: 2, device count: 3, average time / count: 95, average time on device: 31 Seconds (0 Minutes, 31 Seconds)
Next :---------------------------------------------------------------------------
15 September 2012 - 11:03:02 Start, devices: 3, device count: 4 (0.25) (Wu: PG1327_v7.wu)
--------------------------------------------------------------------------- Results: (PG1327_v7.wu)
Device: 0, device count: 4, average time / count: 109, average time on device: 27 Seconds (0 Minutes, 27 Seconds)
Device: 1, device count: 4, average time / count: 108, average time on device: 27 Seconds (0 Minutes, 27 Seconds)
Device: 2, device count: 4, average time / count: 125, average time on device: 31 Seconds (0 Minutes, 31 Seconds)
>> The best average time found: 28 Seconds (0 Minutes, 28 Seconds), with count: 0.33 (3)
4) Message boards : Number crunching : New AstroPulse for GPU ( ATi & NV) released (r1316) (Message 1257920)
Posted 749 days ago by Profile X-Files 27
With or without <cmdline></cmdline> in app_info doesnt pickup the params from ap_cmdline.txt

Did I missed something?
5) Message boards : Number crunching : Inconclusive Work Units Running AP Ver 6 (Message 1231707)
Posted 805 days ago by Profile X-Files 27
Don't know whats wrong with this:
2428927751

This rig has been crunching for awhile now without issues before this.
6) Message boards : Number crunching : Inconclusive Work Units Running AP Ver 6 (Message 1222155)
Posted 825 days ago by Profile X-Files 27
Here's another one:
2409259729
7) Message boards : Number crunching : Inconclusive Work Units Running AP Ver 6 (Message 1222047)
Posted 826 days ago by Profile X-Files 27
First inconclusive after lowering unroll to 6:
2408146504

Its a 30/30.
8) Message boards : Number crunching : Inconclusive Work Units Running AP Ver 6 (Message 1220686)
Posted 828 days ago by Profile X-Files 27
So far so good after lowering it down to 6 from 8. 4 valids and 0 inconclusive so far.
9) Message boards : Number crunching : Inconclusive Work Units Running AP Ver 6 (Message 1220395)
Posted 829 days ago by Profile X-Files 27
Keep in mind most of 560ti are factory overclocked.
Remember my thread at lunatics about this behaviour.

Of the seven hosts I'm tracking so far for inconclusives, only one is running a 560Ti

I've just downloaded 49 inconclusive datafiles from X-Files' GTX 580 with unroll=8 - what do you suggest is wrong with that one?


the inconclusives I checked are all 30 rep pulses.
looks like with unroll 8 on that card it sometimes works and sometimes doesn't.

@ X-Files try and decrease unroll

I will adjust the params once I get home. unroll will be 6.

Other notes:
0.51 for AP and 0.49 for MB
GPUs are OC'ed thru the bios
XFX PRO1250W Black Edition = kill-a-watt says 932W usage
10) Message boards : Number crunching : Inconclusive Work Units Running AP Ver 6 (Message 1220116)
Posted 830 days ago by Profile X-Files 27
Here's my list of Inconclusive:

Are those all from Pending AstroPulse v6 tasks for computer 2340442? With your computers hidden, it would take longer than I'm willing to spend before bedtime to check them all individually.

But with that throughput, we can get a statistical impression of the scale of the problem - 18 valid, 6 invalid for that host as I type implies a 25% failure rate. That's not good, for you or for the project's bandwidth.

Yes its for 2340442 and i don't have this issue with v5.
11) Message boards : Number crunching : Inconclusive Work Units Running AP Ver 6 (Message 1220097)
Posted 830 days ago by Profile X-Files 27
Here's my list of Inconclusive:
2402009700
2401712891
2401149365
2400949559
2400173351
2400167519
2399688500
2399108050
2399007772
2398218968
2398098019
2395607586
2395603227
2395485254
2395484101
2395461657
2394473363
2394244633
2393827071
2393717959
2393435584
2393262477
2393125823
2391546328
2388404565
2384866932
2383779922
2382517326
2382107375
2381632875
2381559982
2381212026
2381140422
2380691271
2378557376
2377286245
2377249863
2376307271
2375792932
2375787448
12) Message boards : Number crunching : BOINC 7.0 released to public (Message 1216390)
Posted 839 days ago by Profile X-Files 27
For those running anonymous platform without <flops> in the app_info.xml there's a possible issue.


What would be the formula for AP NV and MB NV?
13) Message boards : Number crunching : Update for GPU AP (both NV and ATi) to rev560 (Message 1215689)
Posted 840 days ago by Profile X-Files 27
This system doesn't suffer from excessive CPU usage:
Win7, i5-2500k
GTX 570
296.35 (quadro driver using modded inf)




I think at most its using 20% CPU.


Good to know this!
Now it's interesting to know what caused that, your driver version, your Os version or your GPU version... or smth we even can't imagine ;)


Whats bugling me is that I can't replicate this low cpu usage on my other rig - always settled at 85%.
The good thing is that there's no more sleep bug in this NV driver version.
14) Message boards : Number crunching : Update for GPU AP (both NV and ATi) to rev560 (Message 1215168)
Posted 841 days ago by Profile X-Files 27
This system doesn't suffer from excessive CPU usage:
Win7, i5-2500k
GTX 570
296.35 (quadro driver using modded inf)




I think at most its using 20% CPU.
15) Message boards : Number crunching : max/best number of tasks per GTX 580? (Message 1212951)
Posted 847 days ago by Profile X-Files 27
Here's my take on this. My angle of view is the total WUs completed in a given time.

E.g.
Win7
GTX 580

2 Instances:
Elapsed Time: 10 Mins
AR: .42
Total WU completed in 60mins: 12WUs

3 Instances:
Elapsed time: 16 Mins
AR: .42
Total WU completed in 60Mins: 11Wus

Note: Numbers are rounded up


WINNER: 2 Instances
16) Message boards : Number crunching : Kepler ... the good news ... (Message 1209065)
Posted 857 days ago by Profile X-Files 27
The prices on the cards this year are crazy. What's the point of getting a $600 card when some GTX 580s are now below $400?

Initial cost might be lower but longer its not. Less power hungry means less electricity bill.
17) Message boards : Number crunching : A Vote For The Right To Choose Our Own Wingmen??? (Message 1150704)
Posted 1052 days ago by Profile X-Files 27
I agree but I have a suggestion to ease off a little bit for some crunchers who are RAC maniac.

Repair tasks should have a shorter deadline and only send to fast and reliable hosts - just like at WCG. But then again server load will rise up.

After all, this project doesn't need the results pronto.


X, WCG sends to anyone who is actively crunching a project. I don't believe they don't prioritize machines to be sent to.


I was referring to the repair task - WCG has shorter deadline, only send to fast returner and no errors/invalids for certain time.
18) Message boards : Number crunching : A Vote For The Right To Choose Our Own Wingmen??? (Message 1150672)
Posted 1052 days ago by Profile X-Files 27
[quote]IMHO, one of the factors that ensures the sanctity of the project is the random deliverance of WU's to different people. Setting anyone as a pre-set receiver of a specific set of WU's or WU's from a select group of people will eliminate this critical portion of the service.quote]

I agree but I have a suggestion to ease off a little bit for some crunchers who are RAC maniac.

Repair tasks should have a shorter deadline and only send to fast and reliable hosts - just like at WCG. But then again server load will rise up.

After all, this project doesn't need the results pronto.
19) Message boards : Number crunching : Public beta for nVidia AstroPulse, rev 521 (Message 1135892)
Posted 1088 days ago by Profile X-Files 27
No invalids or errors so far with 50+ AP.

using cmd:
-ffa_block 8192 -ffa_block_fetch 2048 -unroll 12 -instances_per_device 3 -hp
cuda count: .34

Seti MB cuda count: .31

http://setiathome.berkeley.edu/results.php?hostid=2340442&offset=0&show_names=0&state=0&appid=5
20) Message boards : Number crunching : Bandwidth split at DSL router. (Message 1057701)
Posted 1317 days ago by Profile X-Files 27
If you wanna control it, use QOS (Quality of Service). But still depends on the reaction time (speed) of the host your trying to communicate.


Next 20

Copyright © 2014 University of California