Posts by Stef42
log in
1) Message boards : News : Testing new apps started (Message 9078)
Posted 30 Sep 2023 by Stef42
I investigated further today. System ran through 6-7K WU's just fine. When the queue is full and stable no issues. Once it ran out yesterday a freeze would sometimes occur. Makes me wonder whether the computer became unstable due to freq/temp/load changes and/or throttling occurred which somehow upset the system. Seems specific enough to me not to think anything is wrong with the app.
2) Message boards : News : Testing new apps started (Message 9076)
Posted 29 Sep 2023 by Stef42
Somehow this new app freezes my computer. It's a HP dual xeon 6148 (AVX-512) system with ECC memory. It can run prime95 just fine, other render software, normal use, load of 100%. Yet when running boinc with specifically this new app, the system randomly freezes. Happens both on Win11 and on Ubuntu (tried to see if W11 was the issue). Anyone else having this issue?

Since the computer freezes, I cannot get any logs that could have been useful. Sorry for that. On W11 it usually happens within the first 30 minutes, on Ubuntu I got the issue after about ±6000 WU's. Heat should not be an issue, as the hardware is rated for longer use and stability.
3) Message boards : News : server outage / db crash again (Message 6572)
Posted 9 Jun 2020 by Stef42
Hi Reb! I hope you are on the lookout that new mandatory updates will be coming this week?
4) Message boards : Number crunching : Trial Factoring (Message 6124)
Posted 11 Apr 2020 by Stef42
Thanks. Still could use results from any recent GPU(Vega 56/64, Radeon VII, etc) Think there's a pretty big speedup possible for the VII - maybe.

Radeon_5500XT
75bits 9% speedup
76bits 8% speedup
77bits 7% speedup


Perftest for Vega56:

Best GPUSieveSize for
SievePrimes: 54 310 1078 1078 1846 2614 3382 5686 8502 13622 19766 31030 47414 74038 113206 175670 270902 419382 647734 1075766
at MiB: 126 126 126 126 126 126 96 96 96 96 126 125 126 126 126 125 126 126 126 126
max M/s: 180990.8 159174.4 152333.5 151507.3 149300.4 146885.5 141073.9 137542.7 133854.8 129138.3 128598.3 118552.8 106635.9 90700.3 72860.6 55293.0 40711.0 28694.4 19716.0 12059.1
Survivors: 48.30% 35.53% 30.01% 30.02% 28.15% 27.07% 26.32% 24.93% 23.95% 22.91% 22.16% 21.31% 20.56% 19.83% 19.19% 18.56% 17.98% 17.44% 16.93% 16.38%
removal rate
average: 93581.3 102616.2 106611.7 106032.0 107274.6 107129.8 103948.8 103256.1 101798.5 99555.0 100098.1 93291.0 84708.7 72710.9 58878.8 45030.2 33390.1 23691.0 16378.2 10083.6
incremental: n/a 168535.3 195585.1 -250.7 191339.1 98317.3 26732.0 76275.5 48893.8 38129.5 229414.4 12955.7 7911.9 4423.2 2385.9 1442.9 892.3 530.5 319.8 170.0

WARNING: Unknown GPU name, assuming GCN. Please post the device name "gfx900 (Advanced Micro Devices, Inc.)" to http://www.mersenneforum.org/showthread.php?t=15646 to have it added to mfakto. Set GPUType in mfakto.ini to select a GPU type yourself to avoid this warning.

5. GPU tf kernels

exponent=2000093 ... calibrating
exponent=2000093, 24575M FCs each, k=73783545359978, 29.889569 GHz-days (assignment), 0.050239 GHz-days (per test): ..............
cl_barrett15_69_gs [60-69]: 2298.24 ms ==> 11212.85M FCs/s ==> 1888.69 GHz-days/day
cl_barrett15_70_gs [60-69]: 2303.40 ms ==> 11187.74M FCs/s ==> 1884.46 GHz-days/day
cl_barrett15_71_gs [60-70]: 2430.70 ms ==> 10601.80M FCs/s ==> 1785.77 GHz-days/day
cl_barrett15_73_gs [60-73]: 2671.47 ms ==> 9646.30M FCs/s ==> 1624.82 GHz-days/day
cl_barrett15_74_gs [60-74]: 2797.03 ms ==> 9213.27M FCs/s ==> 1551.88 GHz-days/day
cl_barrett32_76_gs [64-76]: 2849.72 ms ==> 9042.92M FCs/s ==> 1523.19 GHz-days/day
cl_barrett32_77_gs [64-77]: 3008.85 ms ==> 8564.68M FCs/s ==> 1442.63 GHz-days/day
cl_barrett15_82_gs [60-81]: 3038.97 ms ==> 8479.79M FCs/s ==> 1428.33 GHz-days/day
cl_barrett32_87_gs [65-87]: 3130.80 ms ==> 8231.07M FCs/s ==> 1386.44 GHz-days/day
cl_barrett15_83_gs [60-82]: 3224.75 ms ==> 7991.25M FCs/s ==> 1346.04 GHz-days/day
cl_barrett32_79_gs [64-79]: 3304.79 ms ==> 7797.70M FCs/s ==> 1313.44 GHz-days/day
cl_barrett32_88_gs [65-88]: 3317.56 ms ==> 7767.70M FCs/s ==> 1308.39 GHz-days/day
cl_barrett15_88_gs [60-87]: 3486.45 ms ==> 7391.41M FCs/s ==> 1245.01 GHz-days/day
cl_barrett32_92_gs [65-92]: 3585.27 ms ==> 7187.69M FCs/s ==> 1210.69 GHz-days/day

Resulting speed for M2000093:
bit_min - bit_max GHz-days/day kernelname
60 - 69 1888.690 cl_barrett15_69_gs
69 - 70 1785.765 cl_barrett15_71_gs
70 - 73 1624.820 cl_barrett15_73_gs
73 - 74 1551.882 cl_barrett15_74_gs
74 - 76 1523.188 cl_barrett32_76_gs
76 - 77 1442.633 cl_barrett32_77_gs
77 - 81 1428.333 cl_barrett15_82_gs
81 - 87 1386.439 cl_barrett32_87_gs
87 - 88 1308.390 cl_barrett32_88_gs
88 - 92 1210.692 cl_barrett32_92_gs

exponent=39000037 ... calibrating
exponent=39000037, 12287M FCs each, k=3783943912403, 1.532868 GHz-days (assignment), 0.025120 GHz-days (per test): ..............
cl_barrett15_69_gs [60-69]: 1458.90 ms ==> 8831.91M FCs/s ==> 1487.64 GHz-days/day
cl_barrett15_70_gs [60-69]: 1459.86 ms ==> 8826.13M FCs/s ==> 1486.67 GHz-days/day
cl_barrett15_71_gs [60-70]: 1559.15 ms ==> 8264.06M FCs/s ==> 1392.00 GHz-days/day
cl_barrett15_73_gs [60-73]: 1720.82 ms ==> 7487.65M FCs/s ==> 1261.22 GHz-days/day
cl_barrett15_74_gs [60-74]: 1796.39 ms ==> 7172.65M FCs/s ==> 1208.16 GHz-days/day
cl_barrett32_76_gs [64-76]: 1812.86 ms ==> 7107.52M FCs/s ==> 1197.19 GHz-days/day
cl_barrett32_77_gs [64-77]: 1919.10 ms ==> 6714.03M FCs/s ==> 1130.91 GHz-days/day
cl_barrett15_82_gs [60-81]: 1943.19 ms ==> 6630.80M FCs/s ==> 1116.89 GHz-days/day
cl_barrett32_87_gs [65-87]: 2001.62 ms ==> 6437.23M FCs/s ==> 1084.29 GHz-days/day
cl_barrett15_83_gs [60-82]: 2082.73 ms ==> 6186.54M FCs/s ==> 1042.06 GHz-days/day
cl_barrett32_79_gs [64-79]: 2114.95 ms ==> 6092.28M FCs/s ==> 1026.18 GHz-days/day
cl_barrett32_88_gs [65-88]: 2125.96 ms ==> 6060.75M FCs/s ==> 1020.87 GHz-days/day
cl_barrett15_88_gs [60-87]: 2255.85 ms ==> 5711.77M FCs/s ==> 962.09 GHz-days/day
cl_barrett32_92_gs [65-92]: 2310.29 ms ==> 5577.17M FCs/s ==> 939.42 GHz-days/day

Resulting speed for M39000037:
bit_min - bit_max GHz-days/day kernelname
60 - 69 1487.644 cl_barrett15_69_gs
69 - 70 1391.996 cl_barrett15_71_gs
70 - 73 1261.218 cl_barrett15_73_gs
73 - 74 1208.159 cl_barrett15_74_gs
74 - 76 1197.189 cl_barrett32_76_gs
76 - 77 1130.910 cl_barrett32_77_gs
77 - 81 1116.891 cl_barrett15_82_gs
81 - 87 1084.285 cl_barrett32_87_gs
87 - 88 1020.871 cl_barrett32_88_gs
88 - 92 939.418 cl_barrett32_92_gs

exponent=66362159 ... calibrating
exponent=66362159, 12287M FCs each, k=2223766598517, 0.900843 GHz-days (assignment), 0.025120 GHz-days (per test): ..............
cl_barrett15_69_gs [60-69]: 1463.30 ms ==> 8805.38M FCs/s ==> 1483.18 GHz-days/day
cl_barrett15_70_gs [60-69]: 1464.57 ms ==> 8797.76M FCs/s ==> 1481.89 GHz-days/day
cl_barrett15_71_gs [60-70]: 1564.55 ms ==> 8235.52M FCs/s ==> 1387.19 GHz-days/day
cl_barrett15_73_gs [60-73]: 1727.45 ms ==> 7458.91M FCs/s ==> 1256.38 GHz-days/day
cl_barrett15_74_gs [60-74]: 1805.33 ms ==> 7137.13M FCs/s ==> 1202.18 GHz-days/day
cl_barrett32_76_gs [64-76]: 1815.71 ms ==> 7096.36M FCs/s ==> 1195.31 GHz-days/day
cl_barrett32_77_gs [64-77]: 1921.99 ms ==> 6703.93M FCs/s ==> 1129.21 GHz-days/day
cl_barrett15_82_gs [60-81]: 1949.28 ms ==> 6610.10M FCs/s ==> 1113.40 GHz-days/day
cl_barrett32_87_gs [65-87]: 2004.34 ms ==> 6428.49M FCs/s ==> 1082.81 GHz-days/day
cl_barrett15_83_gs [60-82]: 2090.89 ms ==> 6162.39M FCs/s ==> 1037.99 GHz-days/day
cl_barrett32_79_gs [64-79]: 2119.75 ms ==> 6078.49M FCs/s ==> 1023.86 GHz-days/day
cl_barrett32_88_gs [65-88]: 2129.24 ms ==> 6051.41M FCs/s ==> 1019.30 GHz-days/day
cl_barrett15_88_gs [60-87]: 2264.15 ms ==> 5690.85M FCs/s ==> 958.56 GHz-days/day
cl_barrett32_92_gs [65-92]: 2313.93 ms ==> 5568.42M FCs/s ==> 937.94 GHz-days/day

Resulting speed for M66362159:
bit_min - bit_max GHz-days/day kernelname
60 - 69 1483.176 cl_barrett15_69_gs
69 - 70 1387.188 cl_barrett15_71_gs
70 - 73 1256.376 cl_barrett15_73_gs
73 - 74 1202.176 cl_barrett15_74_gs
74 - 76 1195.308 cl_barrett32_76_gs
76 - 77 1129.208 cl_barrett32_77_gs
77 - 81 1113.403 cl_barrett15_82_gs
81 - 87 1082.814 cl_barrett32_87_gs
87 - 88 1019.297 cl_barrett32_88_gs
88 - 92 937.943 cl_barrett32_92_gs

exponent=74000077 ... calibrating
exponent=74000077, 12287M FCs each, k=1994240527475, 0.807863 GHz-days (assignment), 0.025120 GHz-days (per test): ..............
cl_barrett15_69_gs [60-69]: 1513.23 ms ==> 8514.86M FCs/s ==> 1434.24 GHz-days/day
cl_barrett15_70_gs [60-69]: 1514.76 ms ==> 8506.26M FCs/s ==> 1432.79 GHz-days/day
cl_barrett15_71_gs [60-70]: 1609.10 ms ==> 8007.52M FCs/s ==> 1348.78 GHz-days/day
cl_barrett15_73_gs [60-73]: 1801.98 ms ==> 7150.41M FCs/s ==> 1204.41 GHz-days/day
cl_barrett15_74_gs [60-74]: 1874.75 ms ==> 6872.85M FCs/s ==> 1157.66 GHz-days/day
cl_barrett32_76_gs [64-76]: 1891.18 ms ==> 6813.14M FCs/s ==> 1147.60 GHz-days/day
cl_barrett32_77_gs [64-77]: 2005.54 ms ==> 6424.64M FCs/s ==> 1082.17 GHz-days/day
cl_barrett15_82_gs [60-81]: 2019.86 ms ==> 6379.10M FCs/s ==> 1074.49 GHz-days/day
cl_barrett32_87_gs [65-87]: 2088.75 ms ==> 6168.71M FCs/s ==> 1039.06 GHz-days/day
cl_barrett15_83_gs [60-82]: 2154.64 ms ==> 5980.06M FCs/s ==> 1007.28 GHz-days/day
cl_barrett32_79_gs [64-79]: 2209.47 ms ==> 5831.66M FCs/s ==> 982.28 GHz-days/day
cl_barrett32_88_gs [65-88]: 2223.01 ms ==> 5796.16M FCs/s ==> 976.30 GHz-days/day
cl_barrett15_88_gs [60-87]: 2352.14 ms ==> 5477.95M FCs/s ==> 922.70 GHz-days/day
cl_barrett32_92_gs [65-92]: 2414.48 ms ==> 5336.52M FCs/s ==> 898.88 GHz-days/day

Resulting speed for M74000077:
bit_min - bit_max GHz-days/day kernelname
60 - 69 1434.240 cl_barrett15_69_gs
69 - 70 1348.784 cl_barrett15_71_gs
70 - 73 1204.414 cl_barrett15_73_gs
73 - 74 1157.661 cl_barrett15_74_gs
74 - 76 1147.603 cl_barrett32_76_gs
76 - 77 1082.166 cl_barrett32_77_gs
77 - 81 1074.495 cl_barrett15_82_gs
81 - 87 1039.057 cl_barrett32_87_gs
87 - 88 976.304 cl_barrett32_88_gs
88 - 92 898.882 cl_barrett32_92_gs

exponent=78000071 ... calibrating
exponent=78000071, 12287M FCs each, k=1891972028970, 0.766434 GHz-days (assignment), 0.025120 GHz-days (per test): ..............
cl_barrett15_69_gs [60-69]: 1531.17 ms ==> 8415.06M FCs/s ==> 1417.43 GHz-days/day
cl_barrett15_70_gs [60-69]: 1532.75 ms ==> 8406.39M FCs/s ==> 1415.97 GHz-days/day
cl_barrett15_71_gs [60-70]: 1640.60 ms ==> 7853.76M FCs/s ==> 1322.89 GHz-days/day
cl_barrett15_73_gs [60-73]: 1807.95 ms ==> 7126.79M FCs/s ==> 1200.43 GHz-days/day
cl_barrett15_74_gs [60-74]: 1892.33 ms ==> 6809.01M FCs/s ==> 1146.91 GHz-days/day
cl_barrett32_76_gs [64-76]: 1895.86 ms ==> 6796.35M FCs/s ==> 1144.78 GHz-days/day
cl_barrett32_77_gs [64-77]: 2007.44 ms ==> 6418.56M FCs/s ==> 1081.14 GHz-days/day
cl_barrett15_82_gs [60-81]: 2040.70 ms ==> 6313.96M FCs/s ==> 1063.52 GHz-days/day
cl_barrett32_87_gs [65-87]: 2094.44 ms ==> 6151.97M FCs/s ==> 1036.24 GHz-days/day
cl_barrett15_83_gs [60-82]: 2191.14 ms ==> 5880.45M FCs/s ==> 990.50 GHz-days/day
cl_barrett32_79_gs [64-79]: 2215.02 ms ==> 5817.06M FCs/s ==> 979.82 GHz-days/day
cl_barrett32_88_gs [65-88]: 2225.27 ms ==> 5790.27M FCs/s ==> 975.31 GHz-days/day
cl_barrett15_88_gs [60-87]: 2373.40 ms ==> 5428.87M FCs/s ==> 914.44 GHz-days/day
cl_barrett32_92_gs [65-92]: 2420.25 ms ==> 5323.79M FCs/s ==> 896.74 GHz-days/day

Resulting speed for M78000071:
bit_min - bit_max GHz-days/day kernelname
60 - 69 1417.430 cl_barrett15_69_gs
69 - 70 1322.886 cl_barrett15_71_gs
70 - 73 1200.434 cl_barrett15_73_gs
73 - 74 1146.909 cl_barrett15_74_gs
74 - 76 1144.776 cl_barrett32_76_gs
76 - 77 1081.140 cl_barrett32_77_gs
77 - 81 1063.521 cl_barrett15_82_gs
81 - 87 1036.236 cl_barrett32_87_gs
87 - 88 975.312 cl_barrett32_88_gs
88 - 92 896.739 cl_barrett32_92_gs

exponent=332900047 ... calibrating
exponent=332900047, 12287M FCs each, k=443298082771, 0.179579 GHz-days (assignment), 0.025120 GHz-days (per test): ..............
cl_barrett15_69_gs [60-69]: 1659.15 ms ==> 7765.97M FCs/s ==> 1308.10 GHz-days/day
cl_barrett15_70_gs [60-69]: 1660.44 ms ==> 7759.93M FCs/s ==> 1307.08 GHz-days/day
cl_barrett15_71_gs [60-70]: 1785.75 ms ==> 7215.38M FCs/s ==> 1215.36 GHz-days/day
cl_barrett15_73_gs [60-73]: 1965.40 ms ==> 6555.88M FCs/s ==> 1104.27 GHz-days/day
cl_barrett32_76_gs [64-76]: 2051.63 ms ==> 6280.32M FCs/s ==> 1057.86 GHz-days/day
cl_barrett15_74_gs [60-74]: 2057.36 ms ==> 6262.83M FCs/s ==> 1054.91 GHz-days/day
cl_barrett32_77_gs [64-77]: 2173.76 ms ==> 5927.47M FCs/s ==> 998.42 GHz-days/day
cl_barrett15_82_gs [60-81]: 2218.46 ms ==> 5808.05M FCs/s ==> 978.31 GHz-days/day
cl_barrett32_87_gs [65-87]: 2270.71 ms ==> 5674.40M FCs/s ==> 955.80 GHz-days/day
cl_barrett15_83_gs [60-82]: 2390.30 ms ==> 5390.51M FCs/s ==> 907.98 GHz-days/day
cl_barrett32_79_gs [64-79]: 2403.70 ms ==> 5360.44M FCs/s ==> 902.91 GHz-days/day
cl_barrett32_88_gs [65-88]: 2413.27 ms ==> 5339.18M FCs/s ==> 899.33 GHz-days/day
cl_barrett15_88_gs [60-87]: 2585.18 ms ==> 4984.14M FCs/s ==> 839.53 GHz-days/day
cl_barrett32_92_gs [65-92]: 2629.29 ms ==> 4900.53M FCs/s ==> 825.44 GHz-days/day

Resulting speed for M332900047:
bit_min - bit_max GHz-days/day kernelname
60 - 69 1308.097 cl_barrett15_69_gs
69 - 70 1215.358 cl_barrett15_71_gs
70 - 73 1104.271 cl_barrett15_73_gs
73 - 76 1057.856 cl_barrett32_76_gs
76 - 77 998.422 cl_barrett32_77_gs
77 - 81 978.306 cl_barrett15_82_gs
81 - 87 955.795 cl_barrett32_87_gs
87 - 88 899.331 cl_barrett32_88_gs
88 - 92 825.443 cl_barrett32_92_gs

exponent=999900079 ... calibrating
exponent=999900079, 12287M FCs each, k=147588699800, 0.059788 GHz-days (assignment), 0.025120 GHz-days (per test): ..............
cl_barrett15_69_gs [60-69]: 1706.10 ms ==> 7552.25M FCs/s ==> 1272.10 GHz-days/day
cl_barrett15_70_gs [60-69]: 1707.37 ms ==> 7546.65M FCs/s ==> 1271.16 GHz-days/day
cl_barrett15_71_gs [60-70]: 1818.41 ms ==> 7085.80M FCs/s ==> 1193.53 GHz-days/day
cl_barrett15_73_gs [60-73]: 2027.74 ms ==> 6354.32M FCs/s ==> 1070.32 GHz-days/day
cl_barrett15_74_gs [60-74]: 2125.40 ms ==> 6062.34M FCs/s ==> 1021.14 GHz-days/day
cl_barrett32_76_gs [64-76]: 2126.75 ms ==> 6058.50M FCs/s ==> 1020.49 GHz-days/day
cl_barrett32_77_gs [64-77]: 2258.61 ms ==> 5704.80M FCs/s ==> 960.92 GHz-days/day
cl_barrett15_82_gs [60-81]: 2289.12 ms ==> 5628.76M FCs/s ==> 948.11 GHz-days/day
cl_barrett32_87_gs [65-87]: 2354.52 ms ==> 5472.42M FCs/s ==> 921.77 GHz-days/day
cl_barrett15_83_gs [60-82]: 2446.13 ms ==> 5267.47M FCs/s ==> 887.25 GHz-days/day
cl_barrett32_79_gs [64-79]: 2493.07 ms ==> 5168.29M FCs/s ==> 870.55 GHz-days/day
cl_barrett32_88_gs [65-88]: 2508.22 ms ==> 5137.07M FCs/s ==> 865.29 GHz-days/day
cl_barrett15_88_gs [60-87]: 2676.09 ms ==> 4814.82M FCs/s ==> 811.01 GHz-days/day
cl_barrett32_92_gs [65-92]: 2739.19 ms ==> 4703.91M FCs/s ==> 792.33 GHz-days/day

Resulting speed for M999900079:
bit_min - bit_max GHz-days/day kernelname
60 - 69 1272.099 cl_barrett15_69_gs
69 - 70 1193.530 cl_barrett15_71_gs
70 - 73 1070.321 cl_barrett15_73_gs
73 - 74 1021.140 cl_barrett15_74_gs
74 - 76 1020.493 cl_barrett32_76_gs
76 - 77 960.915 cl_barrett32_77_gs
77 - 81 948.107 cl_barrett15_82_gs
81 - 87 921.772 cl_barrett32_87_gs
87 - 88 865.286 cl_barrett32_88_gs
88 - 92 792.325 cl_barrett32_92_gs

exponent=2001862367 ... calibrating
exponent=2001862367, 12287M FCs each, k=73718331001, 0.029863 GHz-days (assignment), 0.025120 GHz-days (per test): ..............
cl_barrett15_69_gs [60-69]: 1793.85 ms ==> 7182.81M FCs/s ==> 1209.87 GHz-days/day
cl_barrett15_70_gs [60-69]: 1794.08 ms ==> 7181.92M FCs/s ==> 1209.72 GHz-days/day
cl_barrett15_71_gs [60-70]: 1945.07 ms ==> 6624.39M FCs/s ==> 1115.81 GHz-days/day
cl_barrett15_73_gs [60-73]: 2131.80 ms ==> 6044.15M FCs/s ==> 1018.07 GHz-days/day
cl_barrett32_76_gs [64-76]: 2211.33 ms ==> 5826.76M FCs/s ==> 981.46 GHz-days/day
cl_barrett15_74_gs [60-74]: 2233.52 ms ==> 5768.87M FCs/s ==> 971.71 GHz-days/day
cl_barrett32_77_gs [64-77]: 2342.98 ms ==> 5499.37M FCs/s ==> 926.31 GHz-days/day
cl_barrett15_82_gs [60-81]: 2411.51 ms ==> 5343.08M FCs/s ==> 899.99 GHz-days/day
cl_barrett32_87_gs [65-87]: 2451.55 ms ==> 5255.83M FCs/s ==> 885.29 GHz-days/day
cl_barrett32_79_gs [64-79]: 2596.27 ms ==> 4962.85M FCs/s ==> 835.94 GHz-days/day
cl_barrett32_88_gs [65-88]: 2603.56 ms ==> 4948.96M FCs/s ==> 833.60 GHz-days/day
cl_barrett15_83_gs [60-82]: 2613.61 ms ==> 4929.92M FCs/s ==> 830.39 GHz-days/day
cl_barrett15_88_gs [60-87]: 2816.96 ms ==> 4574.04M FCs/s ==> 770.45 GHz-days/day
cl_barrett32_92_gs [65-92]: 2842.20 ms ==> 4533.43M FCs/s ==> 763.61 GHz-days/day

Resulting speed for M2001862367:
bit_min - bit_max GHz-days/day kernelname
60 - 69 1209.870 cl_barrett15_69_gs
69 - 70 1115.811 cl_barrett15_71_gs
70 - 73 1018.075 cl_barrett15_73_gs
73 - 76 981.457 cl_barrett32_76_gs
76 - 77 926.313 cl_barrett32_77_gs
77 - 81 899.988 cl_barrett15_82_gs
81 - 87 885.291 cl_barrett32_87_gs
87 - 88 833.601 cl_barrett32_88_gs
88 - 92 763.609 cl_barrett32_92_gs

exponent=4201971233 ... calibrating
exponent=4201971233, 12287M FCs each, k=35120172035, 0.014227 GHz-days (assignment), 0.025120 GHz-days (per test): ..............
cl_barrett15_69_gs [60-69]: 1831.48 ms ==> 7035.25M FCs/s ==> 1185.02 GHz-days/day
cl_barrett15_70_gs [60-69]: 1832.79 ms ==> 7030.23M FCs/s ==> 1184.17 GHz-days/day
cl_barrett15_71_gs [60-70]: 1952.65 ms ==> 6598.67M FCs/s ==> 1111.48 GHz-days/day
cl_barrett15_73_gs [60-73]: 2180.43 ms ==> 5909.35M FCs/s ==> 995.37 GHz-days/day
cl_barrett32_76_gs [64-76]: 2283.01 ms ==> 5643.82M FCs/s ==> 950.64 GHz-days/day
cl_barrett15_74_gs [60-74]: 2289.70 ms ==> 5627.34M FCs/s ==> 947.87 GHz-days/day
cl_barrett32_77_gs [64-77]: 2428.03 ms ==> 5306.72M FCs/s ==> 893.86 GHz-days/day
cl_barrett15_82_gs [60-81]: 2464.85 ms ==> 5227.45M FCs/s ==> 880.51 GHz-days/day
cl_barrett32_87_gs [65-87]: 2534.26 ms ==> 5084.28M FCs/s ==> 856.40 GHz-days/day
cl_barrett15_83_gs [60-82]: 2639.78 ms ==> 4881.04M FCs/s ==> 822.16 GHz-days/day
cl_barrett32_79_gs [64-79]: 2681.83 ms ==> 4804.52M FCs/s ==> 809.27 GHz-days/day
cl_barrett32_88_gs [65-88]: 2699.66 ms ==> 4772.79M FCs/s ==> 803.93 GHz-days/day
cl_barrett15_88_gs [60-87]: 2887.59 ms ==> 4462.16M FCs/s ==> 751.61 GHz-days/day
cl_barrett32_92_gs [65-92]: 2939.05 ms ==> 4384.04M FCs/s ==> 738.45 GHz-days/day

Resulting speed for M4201971233:
bit_min - bit_max GHz-days/day kernelname
60 - 69 1185.015 cl_barrett15_69_gs
69 - 70 1111.479 cl_barrett15_71_gs
70 - 73 995.370 cl_barrett15_73_gs
73 - 76 950.644 cl_barrett32_76_gs
76 - 77 893.863 cl_barrett32_77_gs
77 - 81 880.510 cl_barrett15_82_gs
81 - 87 856.396 cl_barrett32_87_gs
87 - 88 803.927 cl_barrett32_88_gs
88 - 92 738.446 cl_barrett32_92_gs
5) Message boards : Number crunching : Trial Factoring tests (Message 5974)
Posted 30 Mar 2020 by Stef42
Can you also try with
-d 0
-d 10
-d 11

test with wrapper app, change the job....xml to job.xml and start the wrapper.


How do you start the wrapper standalone?
Could you copy your commandline?
I've tried with chmod, but time and time again returns "no file or directory".

The other -d types where not working. I've also tried every combination in the app_config.xml file with the cmdline, still not working...
6) Message boards : Number crunching : Trial Factoring tests (Message 5971)
Posted 30 Mar 2020 by Stef42
Can anyone post a app_config.xml file that works successfully with a AMD GPU? (Ubuntu, Intel CPU).

I managed to get mfakto running standalone with:
./mfakto-x64 -d 1


Yet, every task in boinc is crashing. As many have reported.

My current app_config.xml:


<app_config>
<app>
<name>GPU72</name>
<max_concurrent>1</max_concurrent>
</app>
<app_version>
<app_name>GPU72</app_name>
<plan_class>opencl_ati_101</plan_class>
<cmdline>-d 1</cmdline>
</app_version>
</app_config>
7) Message boards : Number crunching : Trial Factoring tests (Message 5934)
Posted 29 Mar 2020 by Stef42
Are you sure? The readme states only to support AMD GPU's, since the kernels used are made for AMD GPU's specifically.
8) Message boards : Number crunching : Trial Factoring tests (Message 5932)
Posted 29 Mar 2020 by Stef42
Why run mfakto on a NVIDIA GPU?! That won't work anyway. Mfakto is AMD-GPU only, mfaktc is NVIDIA GPU only.
9) Message boards : Number crunching : Trial Factoring (Message 5873)
Posted 27 Mar 2020 by Stef42
Nvidia on Linux

<message>
process exited with code 195 (0xc3, -61)</message>
<stderr_txt>
22:54:06 (28652): wrapper (7.2.26012): starting
22:54:06 (28652): wrapper: running ./mfaktc.exe ( --device 0)
./mfaktc.exe: error while loading shared libraries: libcudart.so.10.1: cannot open shared object file: No such file or directory
22:54:07 (28652): ./mfaktc.exe exited; CPU time 0.001267
22:54:07 (28652): app exit status: 0x7f00
22:54:07 (28652): called boinc_finish
</stderr_txt>

This code tries running an .exe on Linux! Can be done under WINE (emulator), but not native.


Please see the FAQ, you're missing the CUDA 10.1 toolkit and you need this specific version in order for it to work.
10) Message boards : Number crunching : Trial Factoring (Message 5835)
Posted 22 Mar 2020 by Stef42
If you are able to copy the linux app zip folder to your linux OS and run
./mfaktc.exe -h

for helping to track down the missing app problem.


In most cases, the error is the missing libcudart 10.1 file.
It is included in the lib folder when you download the mfaktc file, but the exe is searching for it in /usr/local/bin. I have no clue how to change this and/or even possible.

I got it working by:
Step 1: install CUDA 10.1 toolkit (exactly 10.1)
https://developer.nvidia.com/cuda-10.1-download-archive-update2?target_os=Linux&target_arch=x86_64&target_distro=Ubuntu&target_version=1804&target_type=deblocal

Step 2: upgraded the driver from Software & Updates (Ubuntu) to v430. Rebooted.

Step 3: run sefltest with ./mfaktc.exe -st (Selftest passed!)

Now that mfaktc.exe is running standalone, using it in BOINC should not pose a problem, although willing to test that!

TLDR: So it seems that the needed libraries are included in the download file, although the executable is not using them. Installing CUDA 10.1 toolkit fixes this.
11) Message boards : Number crunching : Trial Factoring (Message 5831)
Posted 22 Mar 2020 by Stef42
I've setup the linux mfaktc a few weeks ago, had the same problems as you are facing now. I'll try to reinstall and then trace back the steps needed.
12) Message boards : Number crunching : Trial Factoring (Message 5826)
Posted 22 Mar 2020 by Stef42
Working too! (Windows + NVIDIA). Testrun takes about 11-12 minutes.

I would recommend to change the checkpoint interval in the .ini file to 60 seconds perhaps?

On a restart, I lost about 30% of progress:

Mar 22 11:29 | 3440 74.8% | 0.683 2m45s | 1400.43 82485 n.a.%
#
Restart.
#
Mar 22 11:30 | 2088 45.5% | 0.781 6m48s | 1224.71 82485 n.a.%
13) Message boards : Number crunching : Trial Factoring (Message 5802)
Posted 21 Mar 2020 by Stef42
You can read here: https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html

There is also a compiled version voor cuda 8.0, but these nvidia-drivers are old who still use these. FYI: Windows 10 is enforcing v430 at this point via Windows Update, so should be fine I would say.

Or perhaps enforce a minimum driver version in BOINC? Not sure if possible, I'm no developer.
14) Message boards : Number crunching : Trial Factoring (Message 5796)
Posted 21 Mar 2020 by Stef42
On NVIDIA with recent driver versions, this should be ok: https://download.mersenne.ca/mfaktc/mfaktc-0.21/mfaktc-0.21.win.cuda100.zip
(included with correct CUDA library to run out of the box)
15) Message boards : Number crunching : Trial Factoring (Message 5792)
Posted 21 Mar 2020 by Stef42
I believe mfakto cannot be run on nvidia-gpu's, these use mfaktc. That it what I've been doing so far with manual assignments.

Output:
Compiletime options
Select device - Error: No platform found
ERROR: init_CL(3, 0) failed




Main page · Your account · Message boards


Copyright © 2014-2024 BOINC Confederation / rebirther