<<  >> (p.156)
    Author Topic: [LOCKED] cpuminer-opt v3.12.3, open source optimized multi-algo CPU miner  (Read 444193 times)

    • fynxgloire
    Full Member
    ***
    Offline Offline

    Activity: 294
    Merit: 100


    View Profile
    December 21, 2017, 09:53:41 AM
     #3101
    Quote from: Fromage on December 20, 2017, 11:28:36 PM
    Quote from: fynxgloire on December 20, 2017, 09:44:45 PM
    Quote from: Fromage on December 20, 2017, 08:45:32 PM
    Fantastic miner!

    Added to Sniffdog default sse2

    Hi  I am running sniffdog currently for my GPU,
    can you tell me how to use this miner also in Sniffdog?
    Do I have to run 2 sniffdogs on my PC? One for CPU and one for GPU?

    Nope! All in the same startsniffin.bat and you will need to download the latest version of Sniffdog

    I already have the 2.8A version installed and running
    Where are the CPU executables?

    All I see are these subdirectories:
    NVIDIA-Alexis
    NVIDIA-KlausT
    NVIDIA-Palgin
    NVIDIA-TPruvot

    I do not see them anywhere??

  • Fromage
    Sr. Member
    ****
    Offline Offline

    Activity: 338
    Merit: 250


    View Profile WWW
    December 21, 2017, 02:48:46 PM
     #3102
    Quote from: fynxgloire on December 21, 2017, 09:53:41 AM
    Quote from: Fromage on December 20, 2017, 11:28:36 PM
    Quote from: fynxgloire on December 20, 2017, 09:44:45 PM
    Quote from: Fromage on December 20, 2017, 08:45:32 PM
    Fantastic miner!

    Added to Sniffdog default sse2

    Hi  I am running sniffdog currently for my GPU,
    can you tell me how to use this miner also in Sniffdog?
    Do I have to run 2 sniffdogs on my PC? One for CPU and one for GPU?

    Nope! All in the same startsniffin.bat and you will need to download the latest version of Sniffdog

    I already have the 2.8A version installed and running
    Where are the CPU executables?

    All I see are these subdirectories:
    NVIDIA-Alexis
    NVIDIA-KlausT
    NVIDIA-Palgin
    NVIDIA-TPruvot

    I do not see them anywhere??




    Sniffdog 3.0 is the latest version and with all the new updates and bug fixes. Link is below
    Zpool,Multipoolhub,Hashrefinery, ahashpool, and zergpool... SniffDog will sniff you out profits! https://github.com/Sniffdog/Sniffdogminer/releases..... Hashsynminer (multi address (upto 8 different addresses)...multi mining rig splitter(upto 8 cards)).. https://github.com/Sniffdog/Hashsynminer/releases

  • weaponmax
    Newbie
    *
    Offline Offline

    Activity: 1
    Merit: 0


    View Profile
    December 21, 2017, 03:46:43 PM
     #3103
    Hi!
    I have a 7820x, running the cpuminer-aes-avx2.
    How frequently should i be getting shares?
    Code:
    [2017-12-21 16:10:38] Starting Stratum on stratum+tcp://europe.lyra2z-hub.miningpoolhub.com:17025
    [2017-12-21 16:10:38] 16 miner threads started, using 'lyra2z' algorithm.
    [2017-12-21 16:10:39] Stratum difficulty set to 5.25
    [2017-12-21 16:10:40] CPU #5: 65.54 kH, 84.80 kH/s
    [2017-12-21 16:10:40] CPU #11: 65.54 kH, 84.09 kH/s
    [2017-12-21 16:10:40] CPU #6: 65.54 kH, 83.93 kH/s
    [2017-12-21 16:10:40] CPU #7: 65.54 kH, 83.82 kH/s
    [2017-12-21 16:10:40] CPU #1: 65.54 kH, 83.44 kH/s
    [2017-12-21 16:10:40] CPU #3: 65.54 kH, 83.23 kH/s
    [2017-12-21 16:10:40] CPU #15: 65.54 kH, 82.29 kH/s
    [2017-12-21 16:10:40] CPU #14: 65.54 kH, 80.57 kH/s
    [2017-12-21 16:10:40] CPU #13: 65.54 kH, 77.32 kH/s
    [2017-12-21 16:10:40] CPU #2: 65.54 kH, 76.42 kH/s
    [2017-12-21 16:10:40] CPU #4: 65.54 kH, 76.15 kH/s
    [2017-12-21 16:10:40] CPU #9: 65.54 kH, 75.80 kH/s
    [2017-12-21 16:10:40] CPU #8: 65.54 kH, 75.62 kH/s
    [2017-12-21 16:10:40] CPU #12: 65.54 kH, 68.49 kH/s
    [2017-12-21 16:10:40] CPU #10: 65.54 kH, 71.25 kH/s
    [2017-12-21 16:10:40] CPU #0: 65.54 kH, 59.62 kH/s
    [2017-12-21 16:11:30] CPU #0: 3577.25 kH, 71.30 kH/s
    [2017-12-21 16:11:31] CPU #10: 4275.30 kH, 83.62 kH/s
    [2017-12-21 16:11:35] CPU #13: 4639.47 kH, 83.58 kH/s
    [2017-12-21 16:11:37] Stratum difficulty set to 5
    [2017-12-21 16:11:37] CPU #12: 4109.55 kH, 72.35 kH/s
    [2017-12-21 16:11:37] CPU #9: 4548.01 kH, 79.79 kH/s
    [2017-12-21 16:11:37] CPU #2: 4585.23 kH, 80.09 kH/s
    [2017-12-21 16:11:37] CPU #15: 4937.36 kH, 85.86 kH/s
    [2017-12-21 16:11:37] CPU #3: 4993.95 kH, 86.68 kH/s
    [2017-12-21 16:11:38] CPU #1: 5006.67 kH, 86.68 kH/s
    [2017-12-21 16:11:38] CPU #7: 5029.18 kH, 86.32 kH/s
    [2017-12-21 16:11:38] CPU #4: 4569.20 kH, 78.45 kH/s
    [2017-12-21 16:11:39] CPU #6: 5035.64 kH, 85.53 kH/s
    [2017-12-21 16:11:39] CPU #5: 5087.90 kH, 85.89 kH/s
    [2017-12-21 16:11:40] CPU #14: 4833.91 kH, 81.01 kH/s
    [2017-12-21 16:11:41] CPU #11: 5045.35 kH, 82.70 kH/s
    [2017-12-21 16:11:41] CPU #8: 4537.48 kH, 74.38 kH/s
    [2017-12-21 16:12:30] CPU #0: 4278.13 kH, 71.76 kH/s
    [2017-12-21 16:12:37] CPU #9: 4787.25 kH, 79.32 kH/s
    [2017-12-21 16:12:38] CPU #2: 4805.56 kH, 79.20 kH/s
    [2017-12-21 16:12:38] CPU #3: 5200.94 kH, 86.02 kH/s
    [2017-12-21 16:12:38] CPU #7: 5179.36 kH, 86.31 kH/s
    [2017-12-21 16:12:38] CPU #13: 5014.52 kH, 79.68 kH/s
    [2017-12-21 16:12:39] CPU #15: 5151.78 kH, 84.08 kH/s
    [2017-12-21 16:12:39] CPU #1: 5200.98 kH, 84.64 kH/s
    [2017-12-21 16:12:39] CPU #6: 5131.52 kH, 84.98 kH/s
    [2017-12-21 16:12:39] CPU #11: 4961.90 kH, 85.15 kH/s
    [2017-12-21 16:12:39] CPU #5: 5153.53 kH, 85.32 kH/s
    [2017-12-21 16:12:40] CPU #8: 4462.65 kH, 75.75 kH/s
    [2017-12-21 16:12:40] CPU #4: 4707.14 kH, 75.73 kH/s
    [2017-12-21 16:12:42] CPU #12: 4341.00 kH, 66.93 kH/s
    [2017-12-21 16:12:42] CPU #14: 4860.43 kH, 77.34 kH/s
    [2017-12-21 16:12:45] CPU #10: 5017.19 kH, 67.61 kH/s
    [2017-12-21 16:13:29] CPU #0: 4305.70 kH, 73.23 kH/s
    [2017-12-21 16:13:36] CPU #13: 4780.92 kH, 82.24 kH/s
    [2017-12-21 16:13:37] CPU #3: 5161.37 kH, 86.74 kH/s
    [2017-12-21 16:13:37] CPU #15: 5044.65 kH, 85.72 kH/s
    [2017-12-21 16:13:38] CPU #2: 4752.13 kH, 79.34 kH/s
    [2017-12-21 16:13:38] CPU #1: 5078.11 kH, 86.35 kH/s
    [2017-12-21 16:13:38] CPU #10: 4056.34 kH, 77.22 kH/s
    [2017-12-21 16:13:38] CPU #7: 5178.68 kH, 86.25 kH/s
    [2017-12-21 16:13:39] CPU #9: 4759.43 kH, 77.37 kH/s
    [2017-12-21 16:13:39] CPU #12: 4015.68 kH, 70.24 kH/s
    [2017-12-21 16:13:39] CPU #6: 5098.65 kH, 85.15 kH/s
    [2017-12-21 16:13:39] CPU #4: 4544.05 kH, 77.24 kH/s
    [2017-12-21 16:13:39] CPU #5: 5118.91 kH, 85.77 kH/s
    [2017-12-21 16:13:40] CPU #14: 4640.67 kH, 80.69 kH/s
    [2017-12-21 16:13:41] CPU #3: 330.72 kH, 87.31 kH/s
    [2017-12-21 16:13:41] Accepted 1/1 (100%), 71.13 MH, 1295.03 kH/s
    [2017-12-21 16:13:43] CPU #11: 5109.20 kH, 79.99 kH/s
    [2017-12-21 16:13:44] CPU #8: 4544.92 kH, 70.66 kH/s
    [2017-12-21 16:14:25] CPU #10: 3965.49 kH, 83.67 kH/s
    [2017-12-21 16:14:26] Accepted 2/2 (100%), 71.27 MH, 1291.23 kH/s
    [2017-12-21 16:14:30] CPU #0: 4393.88 kH, 71.95 kH/s
    [2017-12-21 16:14:36] CPU #13: 4934.42 kH, 82.94 kH/s
    [2017-12-21 16:14:36] CPU #9: 4642.40 kH, 80.83 kH/s
    [2017-12-21 16:14:37] CPU #15: 5143.28 kH, 85.80 kH/s
    [2017-12-21 16:14:38] CPU #2: 4760.36 kH, 79.54 kH/s
    [2017-12-21 16:14:38] CPU #7: 5175.09 kH, 86.71 kH/s
    [2017-12-21 16:14:38] CPU #1: 5181.28 kH, 85.80 kH/s
    [2017-12-21 16:14:39] CPU #6: 5108.85 kH, 85.45 kH/s
    [2017-12-21 16:14:39] CPU #5: 5146.04 kH, 85.61 kH/s
    [2017-12-21 16:14:40] CPU #4: 4634.46 kH, 76.42 kH/s
    [2017-12-21 16:14:40] CPU #14: 4841.69 kH, 80.24 kH/s
    [2017-12-21 16:14:41] CPU #11: 4799.43 kH, 82.87 kH/s
    [2017-12-21 16:14:42] CPU #3: 5238.40 kH, 86.59 kH/s
    [2017-12-21 16:14:43] CPU #8: 4239.53 kH, 71.53 kH/s
    [2017-12-21 16:14:52] CPU #12: 4214.46 kH, 57.41 kH/s
    [2017-12-21 16:15:25] CPU #10: 5020.03 kH, 83.90 kH/s
    [2017-12-21 16:15:32] CPU #0: 4316.83 kH, 69.57 kH/s
    [2017-12-21 16:15:36] CPU #13: 4976.62 kH, 82.28 kH/s
    [2017-12-21 16:15:37] CPU #9: 4849.66 kH, 80.38 kH/s
    [2017-12-21 16:15:37] CPU #2: 4772.59 kH, 80.22 kH/s
    [2017-12-21 16:15:37] CPU #4: 4585.38 kH, 79.91 kH/s
    [2017-12-21 16:15:37] CPU #1: 5147.76 kH, 86.96 kH/s
    [2017-12-21 16:15:38] CPU #15: 5148.22 kH, 85.20 kH/s
    [2017-12-21 16:15:38] CPU #7: 5202.51 kH, 86.35 kH/s
    [2017-12-21 16:15:39] CPU #8: 4291.55 kH, 77.85 kH/s
    [2017-12-21 16:15:39] CPU #6: 5127.22 kH, 85.67 kH/s
    [2017-12-21 16:15:40] CPU #5: 5136.80 kH, 85.15 kH/s
    [2017-12-21 16:15:40] CPU #11: 4972.19 kH, 83.73 kH/s
    [2017-12-21 16:15:41] CPU #12: 3444.66 kH, 70.74 kH/s
    [2017-12-21 16:15:41] CPU #14: 4814.44 kH, 79.10 kH/s
    [2017-12-21 16:15:42] CPU #3: 5195.11 kH, 86.75 kH/s
    [2017-12-21 16:16:25] CPU #10: 5034.10 kH, 83.72 kH/s
    [2017-12-21 16:16:28] CPU #0: 4174.34 kH, 73.82 kH/s
    [2017-12-21 16:16:37] CPU #9: 4822.97 kH, 79.99 kH/s
    [2017-12-21 16:16:37] CPU #2: 4813.11 kH, 80.12 kH/s
    [2017-12-21 16:16:38] CPU #1: 5217.61 kH, 86.26 kH/s
    [2017-12-21 16:16:38] CPU #7: 5180.70 kH, 86.48 kH/s
    [2017-12-21 16:16:39] CPU #13: 4936.59 kH, 79.50 kH/s
    [2017-12-21 16:16:39] CPU #6: 5140.16 kH, 85.47 kH/s
    [2017-12-21 16:16:39] CPU #5: 5109.02 kH, 85.51 kH/s
    [2017-12-21 16:16:40] CPU #4: 4794.73 kH, 76.77 kH/s
    [2017-12-21 16:16:41] CPU #15: 5111.75 kH, 80.96 kH/s
    [2017-12-21 16:16:41] CPU #11: 5023.96 kH, 82.16 kH/s
    [2017-12-21 16:16:42] CPU #3: 5205.14 kH, 86.34 kH/s
    [2017-12-21 16:16:43] CPU #8: 4670.95 kH, 72.50 kH/s
    [2017-12-21 16:16:45] CPU #12: 4244.44 kH, 66.24 kH/s
    [2017-12-21 16:16:45] CPU #14: 4746.10 kH, 74.16 kH/s
    [2017-12-21 16:17:25] CPU #10: 5023.45 kH, 84.01 kH/s
    [2017-12-21 16:17:29] CPU #0: 4429.10 kH, 72.51 kH/s
    [2017-12-21 16:17:36] CPU #9: 4799.67 kH, 81.03 kH/s
    [2017-12-21 16:17:36] CPU #13: 4769.73 kH, 82.50 kH/s
    [2017-12-21 16:17:38] CPU #2: 4807.06 kH, 79.54 kH/s
    [2017-12-21 16:17:38] CPU #7: 5188.97 kH, 87.07 kH/s
    [2017-12-21 16:17:38] CPU #1: 5175.43 kH, 86.54 kH/s
    [2017-12-21 16:17:38] CPU #15: 4857.76 kH, 85.22 kH/s
    [2017-12-21 16:17:39] CPU #5: 5130.78 kH, 85.92 kH/s
    [2017-12-21 16:17:40] CPU #4: 4606.11 kH, 76.48 kH/s
    [2017-12-21 16:17:40] CPU #6: 5128.05 kH, 83.24 kH/s
    [2017-12-21 16:17:41] CPU #11: 4929.45 kH, 82.94 kH/s
    [2017-12-21 16:17:41] CPU #14: 4449.36 kH, 79.10 kH/s
    [2017-12-21 16:17:42] CPU #3: 5180.65 kH, 86.49 kH/s
    [2017-12-21 16:17:43] CPU #12: 3974.14 kH, 68.53 kH/s
    [2017-12-21 16:17:52] CPU #8: 4349.86 kH, 63.04 kH/s
    [2017-12-21 16:18:25] CPU #10: 5040.52 kH, 83.91 kH/s
    [2017-12-21 16:18:31] CPU #0: 4350.49 kH, 70.41 kH/s
    [2017-12-21 16:18:36] CPU #13: 4949.95 kH, 83.19 kH/s
    [2017-12-21 16:18:36] CPU #9: 4861.74 kH, 80.68 kH/s
    [2017-12-21 16:18:36] CPU #7: 5224.21 kH, 88.82 kH/s
    [2017-12-21 16:18:36] CPU #2: 4772.58 kH, 81.08 kH/s
    [2017-12-21 16:18:37] CPU #1: 5192.42 kH, 87.51 kH/s
    [2017-12-21 16:18:37] CPU #15: 5113.32 kH, 85.91 kH/s
    [2017-12-21 16:18:38] CPU #4: 4589.08 kH, 78.57 kH/s
    [2017-12-21 16:18:39] CPU #5: 5155.06 kH, 85.83 kH/s
    [2017-12-21 16:18:40] CPU #14: 4746.14 kH, 80.74 kH/s
    [2017-12-21 16:18:40] CPU #11: 4976.43 kH, 83.85 kH/s
    [2017-12-21 16:18:41] CPU #8: 3782.38 kH, 77.32 kH/s
    [2017-12-21 16:18:41] CPU #12: 4111.55 kH, 70.59 kH/s
    [2017-12-21 16:18:42] CPU #3: 5189.48 kH, 86.51 kH/s
    [2017-12-21 16:18:54] CPU #6: 4994.18 kH, 68.21 kH/s
    [2017-12-21 16:19:25] CPU #10: 5034.47 kH, 84.04 kH/s
    [2017-12-21 16:19:28] CPU #0: 4224.42 kH, 73.89 kH/s
    [2017-12-21 16:19:32] CPU #1: 4835.62 kH, 87.71 kH/s
    [2017-12-21 16:19:32] Accepted 3/3 (100%), 76.56 MH, 1296.93 kH/s
    [2017-12-21 16:19:35] CPU #13: 4991.49 kH, 84.45 kH/s
    [2017-12-21 16:19:36] CPU #9: 4840.61 kH, 80.64 kH/s
    [2017-12-21 16:19:37] CPU #11: 5031.19 kH, 89.15 kH/s
    [2017-12-21 16:19:37] CPU #2: 4864.53 kH, 80.76 kH/s
    [2017-12-21 16:19:37] CPU #7: 5329.22 kH, 88.15 kH/s
    [2017-12-21 16:19:37] CPU #12: 4235.44 kH, 76.14 kH/s
    [2017-12-21 16:19:37] CPU #15: 5154.50 kH, 85.88 kH/s
    [2017-12-21 16:19:38] CPU #4: 4714.09 kH, 79.47 kH/s
    [2017-12-21 16:19:38] CPU #8: 4639.41 kH, 81.19 kH/s
    [2017-12-21 16:19:39] CPU #14: 4844.45 kH, 82.46 kH/s
    [2017-12-21 16:19:39] CPU #5: 5149.92 kH, 86.03 kH/s
    [2017-12-21 16:19:40] CPU #6: 4092.42 kH, 88.06 kH/s
    [2017-12-21 16:19:40] CPU #3: 5190.38 kH, 88.69 kH/s
    [2017-12-21 16:39:31] lyra2z block 66360, diff 19586.650
    [2017-12-21 16:39:31] CPU #11: 4566 H, 71.83 kH/s
    [2017-12-21 16:39:31] CPU #5: 70 H, 69.79 kH/s
    [2017-12-21 16:39:31] CPU #2: 4573 H, 71.94 kH/s
    [2017-12-21 16:39:31] CPU #15: 3428 H, 56.61 kH/s
    [2017-12-21 16:39:31] CPU #14: 3218 H, 60.11 kH/s
    [2017-12-21 16:39:31] CPU #8: 3386 H, 58.84 kH/s
    [2017-12-21 16:39:31] CPU #7: 4212 H, 67.33 kH/s
    [2017-12-21 16:39:31] CPU #3: 5190.38 kH, 88.69 kH/s
    [2017-12-21 16:39:31] CPU #12: 4483 H, 74.03 kH/s
    [2017-12-21 16:39:31] CPU #4: 4359 H, 73.20 kH/s
    [2017-12-21 16:39:31] CPU #9: 3465 H, 54.51 kH/s
    [2017-12-21 16:39:31] CPU #6: 61 H, 60.82 kH/s
    [2017-12-21 16:39:31] lyra2z block 66361, diff 19586.650
    [2017-12-21 16:39:31] CPU #12: 121 H, 120.52 kH/s
    [2017-12-21 16:39:31] CPU #15: 234 H, 93.34 kH/s
    [2017-12-21 16:39:31] CPU #7: 227 H, 113.22 kH/s
    [2017-12-21 16:39:31] CPU #8: 224 H, 111.72 kH/s
    [2017-12-21 16:39:31] CPU #4: 71 H, 70.72 kH/s
    [2017-12-21 16:39:31] CPU #3: 158 H, 78.80 kH/s
    [2017-12-21 16:39:31] CPU #5: 333 H, 110.74 kH/s
    [2017-12-21 16:39:31] CPU #9: 62 H, 123.26 kH/s
    [2017-12-21 16:39:31] CPU #14: 213 H, 84.96 kH/s
    [2017-12-21 16:39:31] CPU #11: 391 H, 111.36 kH/s
    [2017-12-21 16:39:31] CPU #6: 61 H, 60.82 kH/s
    [2017-12-21 16:39:31] CPU #2: 274 H, 91.12 kH/s
    [2017-12-21 16:40:14] CPU #6: 3649.05 kH, 84.96 kH/s
    [2017-12-21 16:40:25] CPU #3: 4728.18 kH, 86.29 kH/s
    [2017-12-21 16:40:26] CPU #4: 4243.03 kH, 77.01 kH/s
    [2017-12-21 16:40:33] CPU #0: 4433.56 kH, 72.43 kH/s
    [2017-12-21 16:40:33] CPU #1: 5262.38 kH, 85.90 kH/s
    [2017-12-21 16:40:33] CPU #13: 5067.18 kH, 82.57 kH/s
    [2017-12-21 16:40:34] CPU #14: 5097.73 kH, 80.89 kH/s
    [2017-12-21 16:40:36] CPU #15: 5600.32 kH, 85.75 kH/s
    [2017-12-21 16:40:39] CPU #2: 5467.24 kH, 79.73 kH/s
    [2017-12-21 16:40:47] CPU #10: 5042.38 kH, 66.58 kH/s
    [2017-12-21 16:40:48] CPU #5: 6644.50 kH, 85.42 kH/s
    [2017-12-21 16:40:50] CPU #7: 6793.02 kH, 86.06 kH/s
    [2017-12-21 16:40:50] CPU #11: 6681.86 kH, 84.65 kH/s
    [2017-12-21 16:40:58] CPU #8: 6703.24 kH, 76.37 kH/s
    [2017-12-21 16:41:02] CPU #9: 7395.63 kH, 80.61 kH/s
    [2017-12-21 16:41:07] CPU #1: 2912.99 kH, 85.90 kH/s
    [2017-12-21 16:41:07] Accepted 4/4 (100%), 80.46 MH, 1335.75 kH/s
    [2017-12-21 16:41:13] CPU #12: 7231.08 kH, 70.79 kH/s
    [2017-12-21 16:41:13] CPU #6: 5097.58 kH, 85.87 kH/s
    [2017-12-21 16:41:24] CPU #4: 4620.55 kH, 78.77 kH/s
    [2017-12-21 16:41:26] CPU #3: 5177.51 kH, 85.91 kH/s
    [2017-12-21 16:41:32] CPU #0: 4345.54 kH, 73.69 kH/s
    [2017-12-21 16:41:34] CPU #13: 4954.33 kH, 81.55 kH/s
    [2017-12-21 16:41:34] CPU #14: 4853.19 kH, 79.92 kH/s
    [2017-12-21 16:41:36] CPU #15: 5145.03 kH, 85.10 kH/s
    [2017-12-21 16:41:39] CPU #2: 4784.08 kH, 79.61 kH/s
    [2017-12-21 16:41:48] CPU #5: 5125.20 kH, 86.47 kH/s
    [2017-12-21 16:41:49] CPU #7: 5163.88 kH, 86.63 kH/s
    [2017-12-21 16:41:50] CPU #11: 5079.28 kH, 84.72 kH/s
    [2017-12-21 16:41:52] CPU #10: 3994.79 kH, 62.27 kH/s
    [2017-12-21 16:41:58] CPU #8: 4582.12 kH, 76.62 kH/s
    [2017-12-21 16:42:03] CPU #9: 4836.49 kH, 79.81 kH/s
    [2017-12-21 16:42:06] CPU #1: 5154.29 kH, 86.65 kH/s
    [2017-12-21 16:42:11] CPU #12: 4247.53 kH, 73.07 kH/s
    [2017-12-21 16:42:13] CPU #6: 5152.45 kH, 85.64 kH/s
    [2017-12-21 16:42:24] CPU #0: 4421.37 kH, 84.97 kH/s
    [2017-12-21 16:42:24] CPU #4: 4725.99 kH, 79.42 kH/s
    [2017-12-21 16:42:25] CPU #3: 5154.60 kH, 86.89 kH/s
    [2017-12-21 16:42:27] CPU #13: 4893.18 kH, 92.04 kH/s
    [2017-12-21 16:42:33] CPU #14: 4795.47 kH, 82.25 kH/s
    [2017-12-21 16:42:35] CPU #15: 5105.90 kH, 87.17 kH/s
    [2017-12-21 16:42:35] CPU #2: 4776.40 kH, 85.23 kH/s
    [2017-12-21 16:42:40] CPU #7: 5198.02 kH, 102.06 kH/s
    [2017-12-21 16:42:42] CPU #5: 5188.49 kH, 96.08 kH/s
    [2017-12-21 16:42:46] CPU #11: 5083.27 kH, 90.52 kH/s
    [2017-12-21 16:42:49] CPU #10: 3736.22 kH, 64.48 kH/s
    [2017-12-21 16:42:50] CPU #8: 4596.90 kH, 88.44 kH/s
    [2017-12-21 16:42:56] CPU #9: 4788.59 kH, 90.80 kH/s

  • 4ward
    Member
    **
    Offline Offline

    Activity: 473
    Merit: 18


    View Profile
    December 21, 2017, 03:56:50 PM
     #3104
    Quote from: weaponmax on December 21, 2017, 03:46:43 PM
    Hi!
    I have a 7820x, running the cpuminer-aes-avx2.
    How frequently should i be getting shares?
    Code:
    [2017-12-21 16:10:38] Starting Stratum on stratum+tcp://europe.lyra2z-hub.miningpoolhub.com:17025
    [2017-12-21 16:10:38] 16 miner threads started, using 'lyra2z' algorithm.
    [2017-12-21 16:10:39] Stratum difficulty set to 5.25
    [2017-12-21 16:10:40] CPU #5: 65.54 kH, 84.80 kH/s
    [2017-12-21 16:10:40] CPU #11: 65.54 kH, 84.09 kH/s
    [2017-12-21 16:10:40] CPU #6: 65.54 kH, 83.93 kH/s
    [2017-12-21 16:10:40] CPU #7: 65.54 kH, 83.82 kH/s
    [2017-12-21 16:10:40] CPU #1: 65.54 kH, 83.44 kH/s
    [2017-12-21 16:10:40] CPU #3: 65.54 kH, 83.23 kH/s
    [2017-12-21 16:10:40] CPU #15: 65.54 kH, 82.29 kH/s
    [2017-12-21 16:10:40] CPU #14: 65.54 kH, 80.57 kH/s
    [2017-12-21 16:10:40] CPU #13: 65.54 kH, 77.32 kH/s
    [2017-12-21 16:10:40] CPU #2: 65.54 kH, 76.42 kH/s
    [2017-12-21 16:10:40] CPU #4: 65.54 kH, 76.15 kH/s
    [2017-12-21 16:10:40] CPU #9: 65.54 kH, 75.80 kH/s
    [2017-12-21 16:10:40] CPU #8: 65.54 kH, 75.62 kH/s
    [2017-12-21 16:10:40] CPU #12: 65.54 kH, 68.49 kH/s
    [2017-12-21 16:10:40] CPU #10: 65.54 kH, 71.25 kH/s
    [2017-12-21 16:10:40] CPU #0: 65.54 kH, 59.62 kH/s
    [2017-12-21 16:11:30] CPU #0: 3577.25 kH, 71.30 kH/s
    [2017-12-21 16:11:31] CPU #10: 4275.30 kH, 83.62 kH/s
    [2017-12-21 16:11:35] CPU #13: 4639.47 kH, 83.58 kH/s
    [2017-12-21 16:11:37] Stratum difficulty set to 5
    [2017-12-21 16:11:37] CPU #12: 4109.55 kH, 72.35 kH/s
    [2017-12-21 16:11:37] CPU #9: 4548.01 kH, 79.79 kH/s
    [2017-12-21 16:11:37] CPU #2: 4585.23 kH, 80.09 kH/s
    [2017-12-21 16:11:37] CPU #15: 4937.36 kH, 85.86 kH/s
    [2017-12-21 16:11:37] CPU #3: 4993.95 kH, 86.68 kH/s
    [2017-12-21 16:11:38] CPU #1: 5006.67 kH, 86.68 kH/s
    [2017-12-21 16:11:38] CPU #7: 5029.18 kH, 86.32 kH/s
    [2017-12-21 16:11:38] CPU #4: 4569.20 kH, 78.45 kH/s
    [2017-12-21 16:11:39] CPU #6: 5035.64 kH, 85.53 kH/s
    [2017-12-21 16:11:39] CPU #5: 5087.90 kH, 85.89 kH/s
    [2017-12-21 16:11:40] CPU #14: 4833.91 kH, 81.01 kH/s
    [2017-12-21 16:11:41] CPU #11: 5045.35 kH, 82.70 kH/s
    [2017-12-21 16:11:41] CPU #8: 4537.48 kH, 74.38 kH/s
    [2017-12-21 16:12:30] CPU #0: 4278.13 kH, 71.76 kH/s
    [2017-12-21 16:12:37] CPU #9: 4787.25 kH, 79.32 kH/s
    [2017-12-21 16:12:38] CPU #2: 4805.56 kH, 79.20 kH/s
    [2017-12-21 16:12:38] CPU #3: 5200.94 kH, 86.02 kH/s
    [2017-12-21 16:12:38] CPU #7: 5179.36 kH, 86.31 kH/s
    [2017-12-21 16:12:38] CPU #13: 5014.52 kH, 79.68 kH/s
    [2017-12-21 16:12:39] CPU #15: 5151.78 kH, 84.08 kH/s
    [2017-12-21 16:12:39] CPU #1: 5200.98 kH, 84.64 kH/s
    [2017-12-21 16:12:39] CPU #6: 5131.52 kH, 84.98 kH/s
    [2017-12-21 16:12:39] CPU #11: 4961.90 kH, 85.15 kH/s
    [2017-12-21 16:12:39] CPU #5: 5153.53 kH, 85.32 kH/s
    [2017-12-21 16:12:40] CPU #8: 4462.65 kH, 75.75 kH/s
    [2017-12-21 16:12:40] CPU #4: 4707.14 kH, 75.73 kH/s
    [2017-12-21 16:12:42] CPU #12: 4341.00 kH, 66.93 kH/s
    [2017-12-21 16:12:42] CPU #14: 4860.43 kH, 77.34 kH/s
    [2017-12-21 16:12:45] CPU #10: 5017.19 kH, 67.61 kH/s
    [2017-12-21 16:13:29] CPU #0: 4305.70 kH, 73.23 kH/s
    [2017-12-21 16:13:36] CPU #13: 4780.92 kH, 82.24 kH/s
    [2017-12-21 16:13:37] CPU #3: 5161.37 kH, 86.74 kH/s
    [2017-12-21 16:13:37] CPU #15: 5044.65 kH, 85.72 kH/s
    [2017-12-21 16:13:38] CPU #2: 4752.13 kH, 79.34 kH/s
    [2017-12-21 16:13:38] CPU #1: 5078.11 kH, 86.35 kH/s
    [2017-12-21 16:13:38] CPU #10: 4056.34 kH, 77.22 kH/s
    [2017-12-21 16:13:38] CPU #7: 5178.68 kH, 86.25 kH/s
    [2017-12-21 16:13:39] CPU #9: 4759.43 kH, 77.37 kH/s
    [2017-12-21 16:13:39] CPU #12: 4015.68 kH, 70.24 kH/s
    [2017-12-21 16:13:39] CPU #6: 5098.65 kH, 85.15 kH/s
    [2017-12-21 16:13:39] CPU #4: 4544.05 kH, 77.24 kH/s
    [2017-12-21 16:13:39] CPU #5: 5118.91 kH, 85.77 kH/s
    [2017-12-21 16:13:40] CPU #14: 4640.67 kH, 80.69 kH/s
    [2017-12-21 16:13:41] CPU #3: 330.72 kH, 87.31 kH/s
    [2017-12-21 16:13:41] Accepted 1/1 (100%), 71.13 MH, 1295.03 kH/s
    [2017-12-21 16:13:43] CPU #11: 5109.20 kH, 79.99 kH/s
    [2017-12-21 16:13:44] CPU #8: 4544.92 kH, 70.66 kH/s
    [2017-12-21 16:14:25] CPU #10: 3965.49 kH, 83.67 kH/s
    [2017-12-21 16:14:26] Accepted 2/2 (100%), 71.27 MH, 1291.23 kH/s
    [2017-12-21 16:14:30] CPU #0: 4393.88 kH, 71.95 kH/s
    [2017-12-21 16:14:36] CPU #13: 4934.42 kH, 82.94 kH/s
    [2017-12-21 16:14:36] CPU #9: 4642.40 kH, 80.83 kH/s
    [2017-12-21 16:14:37] CPU #15: 5143.28 kH, 85.80 kH/s
    [2017-12-21 16:14:38] CPU #2: 4760.36 kH, 79.54 kH/s
    [2017-12-21 16:14:38] CPU #7: 5175.09 kH, 86.71 kH/s
    [2017-12-21 16:14:38] CPU #1: 5181.28 kH, 85.80 kH/s
    [2017-12-21 16:14:39] CPU #6: 5108.85 kH, 85.45 kH/s
    [2017-12-21 16:14:39] CPU #5: 5146.04 kH, 85.61 kH/s
    [2017-12-21 16:14:40] CPU #4: 4634.46 kH, 76.42 kH/s
    [2017-12-21 16:14:40] CPU #14: 4841.69 kH, 80.24 kH/s
    [2017-12-21 16:14:41] CPU #11: 4799.43 kH, 82.87 kH/s
    [2017-12-21 16:14:42] CPU #3: 5238.40 kH, 86.59 kH/s
    [2017-12-21 16:14:43] CPU #8: 4239.53 kH, 71.53 kH/s
    [2017-12-21 16:14:52] CPU #12: 4214.46 kH, 57.41 kH/s
    [2017-12-21 16:15:25] CPU #10: 5020.03 kH, 83.90 kH/s
    [2017-12-21 16:15:32] CPU #0: 4316.83 kH, 69.57 kH/s
    [2017-12-21 16:15:36] CPU #13: 4976.62 kH, 82.28 kH/s
    [2017-12-21 16:15:37] CPU #9: 4849.66 kH, 80.38 kH/s
    [2017-12-21 16:15:37] CPU #2: 4772.59 kH, 80.22 kH/s
    [2017-12-21 16:15:37] CPU #4: 4585.38 kH, 79.91 kH/s
    [2017-12-21 16:15:37] CPU #1: 5147.76 kH, 86.96 kH/s
    [2017-12-21 16:15:38] CPU #15: 5148.22 kH, 85.20 kH/s
    [2017-12-21 16:15:38] CPU #7: 5202.51 kH, 86.35 kH/s
    [2017-12-21 16:15:39] CPU #8: 4291.55 kH, 77.85 kH/s
    [2017-12-21 16:15:39] CPU #6: 5127.22 kH, 85.67 kH/s
    [2017-12-21 16:15:40] CPU #5: 5136.80 kH, 85.15 kH/s
    [2017-12-21 16:15:40] CPU #11: 4972.19 kH, 83.73 kH/s
    [2017-12-21 16:15:41] CPU #12: 3444.66 kH, 70.74 kH/s
    [2017-12-21 16:15:41] CPU #14: 4814.44 kH, 79.10 kH/s
    [2017-12-21 16:15:42] CPU #3: 5195.11 kH, 86.75 kH/s
    [2017-12-21 16:16:25] CPU #10: 5034.10 kH, 83.72 kH/s
    [2017-12-21 16:16:28] CPU #0: 4174.34 kH, 73.82 kH/s
    [2017-12-21 16:16:37] CPU #9: 4822.97 kH, 79.99 kH/s
    [2017-12-21 16:16:37] CPU #2: 4813.11 kH, 80.12 kH/s
    [2017-12-21 16:16:38] CPU #1: 5217.61 kH, 86.26 kH/s
    [2017-12-21 16:16:38] CPU #7: 5180.70 kH, 86.48 kH/s
    [2017-12-21 16:16:39] CPU #13: 4936.59 kH, 79.50 kH/s
    [2017-12-21 16:16:39] CPU #6: 5140.16 kH, 85.47 kH/s
    [2017-12-21 16:16:39] CPU #5: 5109.02 kH, 85.51 kH/s
    [2017-12-21 16:16:40] CPU #4: 4794.73 kH, 76.77 kH/s
    [2017-12-21 16:16:41] CPU #15: 5111.75 kH, 80.96 kH/s
    [2017-12-21 16:16:41] CPU #11: 5023.96 kH, 82.16 kH/s
    [2017-12-21 16:16:42] CPU #3: 5205.14 kH, 86.34 kH/s
    [2017-12-21 16:16:43] CPU #8: 4670.95 kH, 72.50 kH/s
    [2017-12-21 16:16:45] CPU #12: 4244.44 kH, 66.24 kH/s
    [2017-12-21 16:16:45] CPU #14: 4746.10 kH, 74.16 kH/s
    [2017-12-21 16:17:25] CPU #10: 5023.45 kH, 84.01 kH/s
    [2017-12-21 16:17:29] CPU #0: 4429.10 kH, 72.51 kH/s
    [2017-12-21 16:17:36] CPU #9: 4799.67 kH, 81.03 kH/s
    [2017-12-21 16:17:36] CPU #13: 4769.73 kH, 82.50 kH/s
    [2017-12-21 16:17:38] CPU #2: 4807.06 kH, 79.54 kH/s
    [2017-12-21 16:17:38] CPU #7: 5188.97 kH, 87.07 kH/s
    [2017-12-21 16:17:38] CPU #1: 5175.43 kH, 86.54 kH/s
    [2017-12-21 16:17:38] CPU #15: 4857.76 kH, 85.22 kH/s
    [2017-12-21 16:17:39] CPU #5: 5130.78 kH, 85.92 kH/s
    [2017-12-21 16:17:40] CPU #4: 4606.11 kH, 76.48 kH/s
    [2017-12-21 16:17:40] CPU #6: 5128.05 kH, 83.24 kH/s
    [2017-12-21 16:17:41] CPU #11: 4929.45 kH, 82.94 kH/s
    [2017-12-21 16:17:41] CPU #14: 4449.36 kH, 79.10 kH/s
    [2017-12-21 16:17:42] CPU #3: 5180.65 kH, 86.49 kH/s
    [2017-12-21 16:17:43] CPU #12: 3974.14 kH, 68.53 kH/s
    [2017-12-21 16:17:52] CPU #8: 4349.86 kH, 63.04 kH/s
    [2017-12-21 16:18:25] CPU #10: 5040.52 kH, 83.91 kH/s
    [2017-12-21 16:18:31] CPU #0: 4350.49 kH, 70.41 kH/s
    [2017-12-21 16:18:36] CPU #13: 4949.95 kH, 83.19 kH/s
    [2017-12-21 16:18:36] CPU #9: 4861.74 kH, 80.68 kH/s
    [2017-12-21 16:18:36] CPU #7: 5224.21 kH, 88.82 kH/s
    [2017-12-21 16:18:36] CPU #2: 4772.58 kH, 81.08 kH/s
    [2017-12-21 16:18:37] CPU #1: 5192.42 kH, 87.51 kH/s
    [2017-12-21 16:18:37] CPU #15: 5113.32 kH, 85.91 kH/s
    [2017-12-21 16:18:38] CPU #4: 4589.08 kH, 78.57 kH/s
    [2017-12-21 16:18:39] CPU #5: 5155.06 kH, 85.83 kH/s
    [2017-12-21 16:18:40] CPU #14: 4746.14 kH, 80.74 kH/s
    [2017-12-21 16:18:40] CPU #11: 4976.43 kH, 83.85 kH/s
    [2017-12-21 16:18:41] CPU #8: 3782.38 kH, 77.32 kH/s
    [2017-12-21 16:18:41] CPU #12: 4111.55 kH, 70.59 kH/s
    [2017-12-21 16:18:42] CPU #3: 5189.48 kH, 86.51 kH/s
    [2017-12-21 16:18:54] CPU #6: 4994.18 kH, 68.21 kH/s
    [2017-12-21 16:19:25] CPU #10: 5034.47 kH, 84.04 kH/s
    [2017-12-21 16:19:28] CPU #0: 4224.42 kH, 73.89 kH/s
    [2017-12-21 16:19:32] CPU #1: 4835.62 kH, 87.71 kH/s
    [2017-12-21 16:19:32] Accepted 3/3 (100%), 76.56 MH, 1296.93 kH/s
    [2017-12-21 16:19:35] CPU #13: 4991.49 kH, 84.45 kH/s
    [2017-12-21 16:19:36] CPU #9: 4840.61 kH, 80.64 kH/s
    [2017-12-21 16:19:37] CPU #11: 5031.19 kH, 89.15 kH/s
    [2017-12-21 16:19:37] CPU #2: 4864.53 kH, 80.76 kH/s
    [2017-12-21 16:19:37] CPU #7: 5329.22 kH, 88.15 kH/s
    [2017-12-21 16:19:37] CPU #12: 4235.44 kH, 76.14 kH/s
    [2017-12-21 16:19:37] CPU #15: 5154.50 kH, 85.88 kH/s
    [2017-12-21 16:19:38] CPU #4: 4714.09 kH, 79.47 kH/s
    [2017-12-21 16:19:38] CPU #8: 4639.41 kH, 81.19 kH/s
    [2017-12-21 16:19:39] CPU #14: 4844.45 kH, 82.46 kH/s
    [2017-12-21 16:19:39] CPU #5: 5149.92 kH, 86.03 kH/s
    [2017-12-21 16:19:40] CPU #6: 4092.42 kH, 88.06 kH/s
    [2017-12-21 16:19:40] CPU #3: 5190.38 kH, 88.69 kH/s
    [2017-12-21 16:39:31] lyra2z block 66360, diff 19586.650
    [2017-12-21 16:39:31] CPU #11: 4566 H, 71.83 kH/s
    [2017-12-21 16:39:31] CPU #5: 70 H, 69.79 kH/s
    [2017-12-21 16:39:31] CPU #2: 4573 H, 71.94 kH/s
    [2017-12-21 16:39:31] CPU #15: 3428 H, 56.61 kH/s
    [2017-12-21 16:39:31] CPU #14: 3218 H, 60.11 kH/s
    [2017-12-21 16:39:31] CPU #8: 3386 H, 58.84 kH/s
    [2017-12-21 16:39:31] CPU #7: 4212 H, 67.33 kH/s
    [2017-12-21 16:39:31] CPU #3: 5190.38 kH, 88.69 kH/s
    [2017-12-21 16:39:31] CPU #12: 4483 H, 74.03 kH/s
    [2017-12-21 16:39:31] CPU #4: 4359 H, 73.20 kH/s
    [2017-12-21 16:39:31] CPU #9: 3465 H, 54.51 kH/s
    [2017-12-21 16:39:31] CPU #6: 61 H, 60.82 kH/s
    [2017-12-21 16:39:31] lyra2z block 66361, diff 19586.650
    [2017-12-21 16:39:31] CPU #12: 121 H, 120.52 kH/s
    [2017-12-21 16:39:31] CPU #15: 234 H, 93.34 kH/s
    [2017-12-21 16:39:31] CPU #7: 227 H, 113.22 kH/s
    [2017-12-21 16:39:31] CPU #8: 224 H, 111.72 kH/s
    [2017-12-21 16:39:31] CPU #4: 71 H, 70.72 kH/s
    [2017-12-21 16:39:31] CPU #3: 158 H, 78.80 kH/s
    [2017-12-21 16:39:31] CPU #5: 333 H, 110.74 kH/s
    [2017-12-21 16:39:31] CPU #9: 62 H, 123.26 kH/s
    [2017-12-21 16:39:31] CPU #14: 213 H, 84.96 kH/s
    [2017-12-21 16:39:31] CPU #11: 391 H, 111.36 kH/s
    [2017-12-21 16:39:31] CPU #6: 61 H, 60.82 kH/s
    [2017-12-21 16:39:31] CPU #2: 274 H, 91.12 kH/s
    [2017-12-21 16:40:14] CPU #6: 3649.05 kH, 84.96 kH/s
    [2017-12-21 16:40:25] CPU #3: 4728.18 kH, 86.29 kH/s
    [2017-12-21 16:40:26] CPU #4: 4243.03 kH, 77.01 kH/s
    [2017-12-21 16:40:33] CPU #0: 4433.56 kH, 72.43 kH/s
    [2017-12-21 16:40:33] CPU #1: 5262.38 kH, 85.90 kH/s
    [2017-12-21 16:40:33] CPU #13: 5067.18 kH, 82.57 kH/s
    [2017-12-21 16:40:34] CPU #14: 5097.73 kH, 80.89 kH/s
    [2017-12-21 16:40:36] CPU #15: 5600.32 kH, 85.75 kH/s
    [2017-12-21 16:40:39] CPU #2: 5467.24 kH, 79.73 kH/s
    [2017-12-21 16:40:47] CPU #10: 5042.38 kH, 66.58 kH/s
    [2017-12-21 16:40:48] CPU #5: 6644.50 kH, 85.42 kH/s
    [2017-12-21 16:40:50] CPU #7: 6793.02 kH, 86.06 kH/s
    [2017-12-21 16:40:50] CPU #11: 6681.86 kH, 84.65 kH/s
    [2017-12-21 16:40:58] CPU #8: 6703.24 kH, 76.37 kH/s
    [2017-12-21 16:41:02] CPU #9: 7395.63 kH, 80.61 kH/s
    [2017-12-21 16:41:07] CPU #1: 2912.99 kH, 85.90 kH/s
    [2017-12-21 16:41:07] Accepted 4/4 (100%), 80.46 MH, 1335.75 kH/s
    [2017-12-21 16:41:13] CPU #12: 7231.08 kH, 70.79 kH/s
    [2017-12-21 16:41:13] CPU #6: 5097.58 kH, 85.87 kH/s
    [2017-12-21 16:41:24] CPU #4: 4620.55 kH, 78.77 kH/s
    [2017-12-21 16:41:26] CPU #3: 5177.51 kH, 85.91 kH/s
    [2017-12-21 16:41:32] CPU #0: 4345.54 kH, 73.69 kH/s
    [2017-12-21 16:41:34] CPU #13: 4954.33 kH, 81.55 kH/s
    [2017-12-21 16:41:34] CPU #14: 4853.19 kH, 79.92 kH/s
    [2017-12-21 16:41:36] CPU #15: 5145.03 kH, 85.10 kH/s
    [2017-12-21 16:41:39] CPU #2: 4784.08 kH, 79.61 kH/s
    [2017-12-21 16:41:48] CPU #5: 5125.20 kH, 86.47 kH/s
    [2017-12-21 16:41:49] CPU #7: 5163.88 kH, 86.63 kH/s
    [2017-12-21 16:41:50] CPU #11: 5079.28 kH, 84.72 kH/s
    [2017-12-21 16:41:52] CPU #10: 3994.79 kH, 62.27 kH/s
    [2017-12-21 16:41:58] CPU #8: 4582.12 kH, 76.62 kH/s
    [2017-12-21 16:42:03] CPU #9: 4836.49 kH, 79.81 kH/s
    [2017-12-21 16:42:06] CPU #1: 5154.29 kH, 86.65 kH/s
    [2017-12-21 16:42:11] CPU #12: 4247.53 kH, 73.07 kH/s
    [2017-12-21 16:42:13] CPU #6: 5152.45 kH, 85.64 kH/s
    [2017-12-21 16:42:24] CPU #0: 4421.37 kH, 84.97 kH/s
    [2017-12-21 16:42:24] CPU #4: 4725.99 kH, 79.42 kH/s
    [2017-12-21 16:42:25] CPU #3: 5154.60 kH, 86.89 kH/s
    [2017-12-21 16:42:27] CPU #13: 4893.18 kH, 92.04 kH/s
    [2017-12-21 16:42:33] CPU #14: 4795.47 kH, 82.25 kH/s
    [2017-12-21 16:42:35] CPU #15: 5105.90 kH, 87.17 kH/s
    [2017-12-21 16:42:35] CPU #2: 4776.40 kH, 85.23 kH/s
    [2017-12-21 16:42:40] CPU #7: 5198.02 kH, 102.06 kH/s
    [2017-12-21 16:42:42] CPU #5: 5188.49 kH, 96.08 kH/s
    [2017-12-21 16:42:46] CPU #11: 5083.27 kH, 90.52 kH/s
    [2017-12-21 16:42:49] CPU #10: 3736.22 kH, 64.48 kH/s
    [2017-12-21 16:42:50] CPU #8: 4596.90 kH, 88.44 kH/s
    [2017-12-21 16:42:56] CPU #9: 4788.59 kH, 90.80 kH/s

    this is normal, lyra2z on mph has high starting difficulty, it gets better after some time
    Forager - MultiPool profit switching multi-miner with MSI Afterburner integration

  • joblo (OP)
    Legendary
    *
    Offline Offline

    Activity: 1470
    Merit: 1114


    View Profile
    December 21, 2017, 05:01:53 PM
     #3105
    Quote from: babooza88 on December 21, 2017, 02:52:18 AM
    is it just me or is this super difficult to install? i'm an unix/dba admin (not a programmer) and this is impossible to compile. trying to compile it with static libs so i can use it across multiple machines, but no matter what i do (yes i followed all tutorials online) nothin works

    There's only one tutorial that matters,

    README.md
    Quote
    See file RELEASE_NOTES for change log and compile instructions.
    AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
    https://bt.irlbtc.com/view/5226770.msg53865575#msg53865575
    BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,

  • joblo (OP)
    Legendary
    *
    Offline Offline

    Activity: 1470
    Merit: 1114


    View Profile
    December 21, 2017, 05:11:52 PM
     #3106
    Quote from: 4ward on December 21, 2017, 07:03:25 AM
    Quote from: nizzuu on December 21, 2017, 05:57:15 AM
    Quote from: rukez on December 20, 2017, 08:51:17 PM
    Sir, where did you find this info? Cache Block diagram looks exactly like the one from sandy bridge times, everything seems to be the same as inside kaby.

    Nope, the structure is the same, but the amount increased. This leads to better mining performance in cache-bound algos, and better flexibility (w/o looking at core count). E.g. on i5 8600K you may now use 2 double threads for cryptonight (2x4Mb) at around 320+ H/s and you will be able to use the rest (1Mb) for video decoding (which uses cache as well). This is good, and affects power consumption and heating (in a good way) as well.

    It's the same 2Mb per core on i7 and 1.5Mb per core on i5, just more cores. So no real changes

    There's no chnage in architecture that I'm aware of, everything seems to be scaled 1.5 vs previous generation,
    no compile differences, no source code differences.

    It's not a SW issue, I'm doubtful it's a Coffeelake issue. It might be an issue with that specific CPU or system.
    More data is required including from other Coffeelake owners.

    OP has been quiet for a couple of days, maybe it's no longer an issue.
    AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
    https://bt.irlbtc.com/view/5226770.msg53865575#msg53865575
    BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,

  • guytechie
    Hero Member
    *****
    Offline Offline

    Activity: 677
    Merit: 500


    View Profile
    December 21, 2017, 06:41:42 PM
    Last edit: December 21, 2017, 06:55:28 PM by guytechie
     #3107
    Quote from: Fromage on December 21, 2017, 02:48:46 PM
    Quote from: fynxgloire on December 21, 2017, 09:53:41 AM
    Quote from: Fromage on December 20, 2017, 11:28:36 PM
    Quote from: fynxgloire on December 20, 2017, 09:44:45 PM
    Quote from: Fromage on December 20, 2017, 08:45:32 PM
    Fantastic miner!

    Added to Sniffdog default sse2

    Hi  I am running sniffdog currently for my GPU,
    can you tell me how to use this miner also in Sniffdog?
    Do I have to run 2 sniffdogs on my PC? One for CPU and one for GPU?

    Nope! All in the same startsniffin.bat and you will need to download the latest version of Sniffdog

    I already have the 2.8A version installed and running
    Where are the CPU executables?

    All I see are these subdirectories:
    NVIDIA-Alexis
    NVIDIA-KlausT
    NVIDIA-Palgin
    NVIDIA-TPruvot

    I do not see them anywhere??




    Sniffdog 3.0 is the latest version and with all the new updates and bug fixes. Link is below

    Bugs?
    1. Trying out Sniffdog 3.0 and I don't even see yescrypt (cpuminer-opt) listed as Benchmarked (inactive list after it's done).  Did it even run?

    2. It keeps downloading Excavator.  I think I see why.

    ExcavatorNvidia.ps1:
    Code:
    $Path = ".\Bin\Excavator\excavator.exe"

    Actual path:
    Code:
    $Path = ".\Bin\Excavator\excavator\excavator.exe"

    There's another "excavator" directory after it's extracted.

    Questions:
    1. Are you able to get it to mine with both GPU and CPU at the same time?  In my experience, both can be mining at the same time without affecting each other's performance (or if they do, it's negligible).

    2. Can you also add M7M and enable XEVAN for cpuminer-opt?  Those algos are pretty good for CPU mining and supported in at least 3 of the pools (zpool, ahash, and hash).
    Put something in my tip jar if I made your day. Smiley
    BTC:
    1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu

  • Fromage
    Sr. Member
    ****
    Offline Offline

    Activity: 338
    Merit: 250


    View Profile WWW
    December 21, 2017, 10:23:02 PM
    Last edit: December 21, 2017, 11:08:31 PM by Fromage
     #3108
    Quote from: guytechie on December 21, 2017, 06:41:42 PM
    Quote from: Fromage on December 21, 2017, 02:48:46 PM
    Quote from: fynxgloire on December 21, 2017, 09:53:41 AM
    Quote from: Fromage on December 20, 2017, 11:28:36 PM
    Quote from: fynxgloire on December 20, 2017, 09:44:45 PM
    Quote from: Fromage on December 20, 2017, 08:45:32 PM
    Fantastic miner!

    Added to Sniffdog default sse2

    Hi  I am running sniffdog currently for my GPU,
    can you tell me how to use this miner also in Sniffdog?
    Do I have to run 2 sniffdogs on my PC? One for CPU and one for GPU?

    Nope! All in the same startsniffin.bat and you will need to download the latest version of Sniffdog

    I already have the 2.8A version installed and running
    Where are the CPU executables?

    All I see are these subdirectories:
    NVIDIA-Alexis
    NVIDIA-KlausT
    NVIDIA-Palgin
    NVIDIA-TPruvot

    I do not see them anywhere??




    Sniffdog 3.0 is the latest version and with all the new updates and bug fixes. Link is below

    Bugs?
    1. Trying out Sniffdog 3.0 and I don't even see yescrypt (cpuminer-opt) listed as Benchmarked (inactive list after it's done).  Did it even run?

    2. It keeps downloading Excavator.  I think I see why.

    ExcavatorNvidia.ps1:
    Code:
    $Path = ".\Bin\Excavator\excavator.exe"

    Actual path:
    Code:
    $Path = ".\Bin\Excavator\excavator\excavator.exe"

    There's another "excavator" directory after it's extracted.

    Questions:
    1. Are you able to get it to mine with both GPU and CPU at the same time?  In my experience, both can be mining at the same time without affecting each other's performance (or if they do, it's negligible).

    2. Can you also add M7M and enable XEVAN for cpuminer-opt?  Those algos are pretty good for CPU mining and supported in at least 3 of the pools (zpool, ahash, and hash).




    Yes.... add yescrypt to startsniffin.bat

    Excavator is a manual movement on your part to move it back one folder....please read the notes

    Also, updated to 3.1... added ethereum/siacoin Claymore miner... opened decred in tpruvot Ccminer and added three more algo's (yescrypt,decred, and ethash) to startsniffin.bat and updated klaust 8.17

    EDIT: Yes you are right about the constant downloading of excavator... I turned off all algo's in the ExcavatorNvidia.ps1 in the Miners folder and added more to info....

    Thank you for showing me this Smiley We do not want to make it easy to get excavator running but yet have it for the more advanced users
    Zpool,Multipoolhub,Hashrefinery, ahashpool, and zergpool... SniffDog will sniff you out profits! https://github.com/Sniffdog/Sniffdogminer/releases..... Hashsynminer (multi address (upto 8 different addresses)...multi mining rig splitter(upto 8 cards)).. https://github.com/Sniffdog/Hashsynminer/releases

  • guytechie
    Hero Member
    *****
    Offline Offline

    Activity: 677
    Merit: 500


    View Profile
    December 22, 2017, 01:45:10 AM
     #3109
    Quote from: Fromage on December 21, 2017, 10:23:02 PM
    Quote from: guytechie on December 21, 2017, 06:41:42 PM
    Quote from: Fromage on December 21, 2017, 02:48:46 PM
    Quote from: fynxgloire on December 21, 2017, 09:53:41 AM
    Quote from: Fromage on December 20, 2017, 11:28:36 PM
    Quote from: fynxgloire on December 20, 2017, 09:44:45 PM
    Quote from: Fromage on December 20, 2017, 08:45:32 PM
    Fantastic miner!

    Added to Sniffdog default sse2

    Hi  I am running sniffdog currently for my GPU,
    can you tell me how to use this miner also in Sniffdog?
    Do I have to run 2 sniffdogs on my PC? One for CPU and one for GPU?

    Nope! All in the same startsniffin.bat and you will need to download the latest version of Sniffdog

    I already have the 2.8A version installed and running
    Where are the CPU executables?

    All I see are these subdirectories:
    NVIDIA-Alexis
    NVIDIA-KlausT
    NVIDIA-Palgin
    NVIDIA-TPruvot

    I do not see them anywhere??




    Sniffdog 3.0 is the latest version and with all the new updates and bug fixes. Link is below

    Bugs?
    1. Trying out Sniffdog 3.0 and I don't even see yescrypt (cpuminer-opt) listed as Benchmarked (inactive list after it's done).  Did it even run?

    2. It keeps downloading Excavator.  I think I see why.

    ExcavatorNvidia.ps1:
    Code:
    $Path = ".\Bin\Excavator\excavator.exe"

    Actual path:
    Code:
    $Path = ".\Bin\Excavator\excavator\excavator.exe"

    There's another "excavator" directory after it's extracted.

    Questions:
    1. Are you able to get it to mine with both GPU and CPU at the same time?  In my experience, both can be mining at the same time without affecting each other's performance (or if they do, it's negligible).

    2. Can you also add M7M and enable XEVAN for cpuminer-opt?  Those algos are pretty good for CPU mining and supported in at least 3 of the pools (zpool, ahash, and hash).




    Yes.... add yescrypt to startsniffin.bat

    Excavator is a manual movement on your part to move it back one folder....please read the notes

    Also, updated to 3.1... added ethereum/siacoin Claymore miner... opened decred in tpruvot Ccminer and added three more algo's (yescrypt,decred, and ethash) to startsniffin.bat and updated klaust 8.17

    EDIT: Yes you are right about the constant downloading of excavator... I turned off all algo's in the ExcavatorNvidia.ps1 in the Miners folder and added more to info....

    Thank you for showing me this Smiley We do not want to make it easy to get excavator running but yet have it for the more advanced users

    Ah, yes, I did miss the note about Excavator.  I enabled it - it's actually faster than whatever ccminer-based the algos previously used.

    Any plans on adding m7m and xevan mining on cpuminer-opt?  Would be great to be able to auto-switch between pools and cpu-based algos as well.

    Out of all the auto-switching scripts, this is the most complete I've come across.  Thanks. Smiley
    Put something in my tip jar if I made your day. Smiley
    BTC:
    1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu

  • Fromage
    Sr. Member
    ****
    Offline Offline

    Activity: 338
    Merit: 250


    View Profile WWW
    December 22, 2017, 03:06:59 AM
     #3110
    Quote from: guytechie on December 22, 2017, 01:45:10 AM
    Quote from: Fromage on December 21, 2017, 10:23:02 PM
    Quote from: guytechie on December 21, 2017, 06:41:42 PM
    Quote from: Fromage on December 21, 2017, 02:48:46 PM
    Quote from: fynxgloire on December 21, 2017, 09:53:41 AM
    Quote from: Fromage on December 20, 2017, 11:28:36 PM
    Quote from: fynxgloire on December 20, 2017, 09:44:45 PM
    Quote from: Fromage on December 20, 2017, 08:45:32 PM
    Fantastic miner!

    Added to Sniffdog default sse2

    Hi  I am running sniffdog currently for my GPU,
    can you tell me how to use this miner also in Sniffdog?
    Do I have to run 2 sniffdogs on my PC? One for CPU and one for GPU?

    Nope! All in the same startsniffin.bat and you will need to download the latest version of Sniffdog

    I already have the 2.8A version installed and running
    Where are the CPU executables?

    All I see are these subdirectories:
    NVIDIA-Alexis
    NVIDIA-KlausT
    NVIDIA-Palgin
    NVIDIA-TPruvot

    I do not see them anywhere??




    Sniffdog 3.0 is the latest version and with all the new updates and bug fixes. Link is below

    Bugs?
    1. Trying out Sniffdog 3.0 and I don't even see yescrypt (cpuminer-opt) listed as Benchmarked (inactive list after it's done).  Did it even run?

    2. It keeps downloading Excavator.  I think I see why.

    ExcavatorNvidia.ps1:
    Code:
    $Path = ".\Bin\Excavator\excavator.exe"

    Actual path:
    Code:
    $Path = ".\Bin\Excavator\excavator\excavator.exe"

    There's another "excavator" directory after it's extracted.

    Questions:
    1. Are you able to get it to mine with both GPU and CPU at the same time?  In my experience, both can be mining at the same time without affecting each other's performance (or if they do, it's negligible).

    2. Can you also add M7M and enable XEVAN for cpuminer-opt?  Those algos are pretty good for CPU mining and supported in at least 3 of the pools (zpool, ahash, and hash).




    Yes.... add yescrypt to startsniffin.bat

    Excavator is a manual movement on your part to move it back one folder....please read the notes

    Also, updated to 3.1... added ethereum/siacoin Claymore miner... opened decred in tpruvot Ccminer and added three more algo's (yescrypt,decred, and ethash) to startsniffin.bat and updated klaust 8.17

    EDIT: Yes you are right about the constant downloading of excavator... I turned off all algo's in the ExcavatorNvidia.ps1 in the Miners folder and added more to info....

    Thank you for showing me this Smiley We do not want to make it easy to get excavator running but yet have it for the more advanced users

    Ah, yes, I did miss the note about Excavator.  I enabled it - it's actually faster than whatever ccminer-based the algos previously used.

    Any plans on adding m7m and xevan mining on cpuminer-opt?  Would be great to be able to auto-switch between pools and cpu-based algos as well.

    Out of all the auto-switching scripts, this is the most complete I've come across.  Thanks. Smiley

    if there was a pool open with m7m I would, Also tried with xevan and Sniffdog just deleted the algo from the cpu cause no shares were found

    Yes thank you. After numerous patches... it's ready for more

    I'm very excited in the new year to try JayDDee cpuminer....like a kid in a candy store
    Zpool,Multipoolhub,Hashrefinery, ahashpool, and zergpool... SniffDog will sniff you out profits! https://github.com/Sniffdog/Sniffdogminer/releases..... Hashsynminer (multi address (upto 8 different addresses)...multi mining rig splitter(upto 8 cards)).. https://github.com/Sniffdog/Hashsynminer/releases

  • babooza88
    Newbie
    *
    Offline Offline

    Activity: 2
    Merit: 0


    View Profile
    December 22, 2017, 09:49:14 PM
     #3111
    help please...

    i have 2 compiled versions of cpuminer-opt
    v1 = without march=native, SW features: SSE2.
    v2 = with march=native, SW features: SSE2 AES AVX AVX2.

    why is it sometimes v1 doesn't work on a machine and sometimes v2 doesn't work?? it's like 50/50 which version works. even if CPU has AES, sometimes v2 doesn't work

  • guytechie
    Hero Member
    *****
    Offline Offline

    Activity: 677
    Merit: 500


    View Profile
    December 22, 2017, 11:56:07 PM
     #3112
    Quote from: Fromage on December 22, 2017, 03:06:59 AM

    if there was a pool open with m7m I would, Also tried with xevan and Sniffdog just deleted the algo from the cpu cause no shares were found

    Yes thank you. After numerous patches... it's ready for more

    I'm very excited in the new year to try JayDDee cpuminer....like a kid in a candy store

    Yeah, I can't wait for m7m to be back.  I'm anxious to finally see the performance difference with SHA optimizations.

    cpuminer-opt says Yescrypt uses both AVX2 and SHA, but I don't see much difference in hashrate.
    Put something in my tip jar if I made your day. Smiley
    BTC:
    1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu

  • joblo (OP)
    Legendary
    *
    Offline Offline

    Activity: 1470
    Merit: 1114


    View Profile
    December 23, 2017, 01:59:44 AM
    Last edit: December 23, 2017, 02:29:43 AM by joblo
     #3113
    Quote from: guytechie on December 22, 2017, 11:56:07 PM

    Yeah, I can't wait for m7m to be back.  I'm anxious to finally see the performance difference with SHA optimizations.

    cpuminer-opt says Yescrypt uses both AVX2 and SHA, but I don't see much difference in hashrate.

    That isn't quite correct, there's no AVX in yescrypt (I'll fix that), but there is SHA. Does it say it's mining with SHA?
    If Linux do you have openssl 1.1? If Windows are you using SHA build?
    AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
    https://bt.irlbtc.com/view/5226770.msg53865575#msg53865575
    BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,

  • guytechie
    Hero Member
    *****
    Offline Offline

    Activity: 677
    Merit: 500


    View Profile
    December 23, 2017, 09:01:33 PM
     #3114
    Quote from: joblo on December 23, 2017, 01:59:44 AM
    Quote from: guytechie on December 22, 2017, 11:56:07 PM

    Yeah, I can't wait for m7m to be back.  I'm anxious to finally see the performance difference with SHA optimizations.

    cpuminer-opt says Yescrypt uses both AVX2 and SHA, but I don't see much difference in hashrate.

    That isn't quite correct, there's no AVX in yescrypt (I'll fix that), but there is SHA. Does it say it's mining with SHA?
    If Linux do you have openssl 1.1? If Windows are you using SHA build?

    Using Windows SHA build.

    Code:
             **********  cpuminer-opt 3.7.7  ***********
         A CPU miner with multi algo support and optimized for CPUs
         with AES_NI and AVX2 and SHA extensions.
         BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT

    CPU: AMD Ryzen Threadripper 1950X 16-Core Processor .
    SW built on Dec 18 2017 with GCC 5.3.1.
    CPU features: SSE2 AES AVX AVX2 SHA.
    SW features: SSE2 AES AVX AVX2 4WAY SHA.
    Algo features: SSE2 AVX AVX2 SHA.
    Start mining with AVX2 SHA.
    Put something in my tip jar if I made your day. Smiley
    BTC:
    1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu

  • nizzuu
    Full Member
    ***
    Offline Offline

    Activity: 187
    Merit: 100

    Cryptocurrency enthusiast


    View Profile
    December 24, 2017, 07:57:18 PM
     #3115
    Can anybody tell some thing about L2/L3 cache usage? E.g., I got a 16-core CPU, it has 16Mb L2 and 16Mb L3. So, if the thread count and cpuminer-opt option "--cpu-affinity" are both set correctly, will the (e.g. cryptonight - 2Mb per thread) faster L2 cache be used instead of L3? Or the L2 size does not affect?

  • 4ward
    Member
    **
    Offline Offline

    Activity: 473
    Merit: 18


    View Profile
    December 24, 2017, 09:06:20 PM
     #3116
    Quote from: nizzuu on December 24, 2017, 07:57:18 PM
    Can anybody tell some thing about L2/L3 cache usage? E.g., I got a 16-core CPU, it has 16Mb L2 and 16Mb L3. So, if the thread count and cpuminer-opt option "--cpu-affinity" are both set correctly, will the (e.g. cryptonight - 2Mb per thread) faster L2 cache be used instead of L3? Or the L2 size does not affect?

    L2 cache is faster than L3 and holds core specific cache which prevents from other cores overriding that cache every time.
    L3 is shared among the cores and is slightly slower.
    Theoretically, with 16MB of L2 cache, 8 threads will provide the highest hash rate.
    I'm not sure how much exactly L3 cache will benefit, but it will definitely speed up memory read operations
    Forager - MultiPool profit switching multi-miner with MSI Afterburner integration

  • joblo (OP)
    Legendary
    *
    Offline Offline

    Activity: 1470
    Merit: 1114


    View Profile
    December 24, 2017, 10:35:13 PM
     #3117
    If L2 cache is the same size as L3 there would be no use for L3.

    Ryzen has 2 MB L2 per 4 core CCX, or 512 kB per core.
    AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
    https://bt.irlbtc.com/view/5226770.msg53865575#msg53865575
    BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,

  • nizzuu
    Full Member
    ***
    Offline Offline

    Activity: 187
    Merit: 100

    Cryptocurrency enthusiast


    View Profile
    December 25, 2017, 05:19:17 AM
    Last edit: December 25, 2017, 11:53:52 AM by nizzuu
     #3118
    Quote from: ypsi on December 24, 2017, 09:46:21 PM
    What 16-core model is that exactly that has the same L2 size as L3? The new bronze-gold-platinum still has a higher L3 than L2.

    It's not so "cool" that you may think - it's AMD Opteron X16 6274. This one is old, yep, but it looks something like this:

    http://www.pixic.ru/i/V0B1T4Y737K7s3v0.png

    So, AVX and AES support is present. I have 2 of them, the only lack (for complete set) is the motherboard (dual-cpu), which costs $65 in China and is capable of holding 5GPUs on pci-e gen 2 as well.

    This screenshot is of another model, mines have 8x2048 16-way L2, and 16Mb 128-way L3. Memory is ddr3-1800 (4 pieces of 4Gb for each cpu), so it's going to be quad-channel.

    Will be interesting to test, the sender sends the motherboard to me in early february 2018.

    Seems that AMD-specific intrinsics http://developer.amd.com/wordpress/media/2012/10/New-Bulldozer-and-Piledriver-Instructions.pdf are not used by cpuminer-opt, but I'm unsure they could give any speed gain. This will be my first AMD cpu after 486-DX2-66 lol Grin

  • joblo (OP)
    Legendary
    *
    Offline Offline

    Activity: 1470
    Merit: 1114


    View Profile
    December 26, 2017, 06:21:56 PM
     #3119
    This is a reminder to Windows binaries users. I intend to make some changes in the next release
    to reduce the number of binaries I have to build each release.

    I would like to drop the sse42 (Nehalem) build. Nehalem users would be forced to use the sse2 build.
    There is no sse42 targetted code in any algos that I'm aware of so  there should be no difference in
    performance. Please report if you have data that shows otherwise.

    AVX2 performance on Ryzen is still questionable. It was suggested I provide a avx-sha build. I will provide
    either a avx-sha or avx2-sha build. This will not apply to 4way as it requires AVX2. Ryzen users please
    test avx vs avx2 (not 4way) to determine which gets the best performance. The best algo to test AVX2
    is lyra2rev2 as it has the most AVX2 code.
    AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
    https://bt.irlbtc.com/view/5226770.msg53865575#msg53865575
    BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,

  • guytechie
    Hero Member
    *****
    Offline Offline

    Activity: 677
    Merit: 500


    View Profile
    December 26, 2017, 06:54:33 PM
     #3120
    Quote from: joblo on December 26, 2017, 06:21:56 PM
    This is a reminder to Windows binaries users. I intend to make some changes in the next release
    to reduce the number of binaries I have to build each release.

    I would like to drop the sse42 (Nehalem) build. Nehalem users would be forced to use the sse2 build.
    There is no sse42 targetted code in any algos that I'm aware of so  there should be no difference in
    performance. Please report if you have data that shows otherwise.

    AVX2 performance on Ryzen is still questionable. It was suggested I provide a avx-sha build. I will provide
    either a avx-sha or avx2-sha build. This will not apply to 4way as it requires AVX2. Ryzen users please
    test avx vs avx2 (not 4way) to determine which gets the best performance. The best algo to test AVX2
    is lyra2rev2 as it has the most AVX2 code.

    Ryzen 1700 at 3.7 GHz (16 threads)

    cpuminer-avx.exe
    ~140 kH/s per thread.

    cpuminer-avx2.exe
    ~133 kH/s per thread.

    cpuminer-4way.exe
    ~133 kH/s per thread.

    cpuminer-sse2.exe
    ~135 kH/s per thread


    I think you're right about Ryzen and the poor avx2 performance.  Maybe compile with avx-sha?
    Put something in my tip jar if I made your day. Smiley
    BTC:
    1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu
    Pages: « 1 ... 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 [156] 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 »
      Print  
Page 155
Viewing Page: 156

IRLBTC™ © 2025 IRLBTC.com