CryptoGraphics / lyclMiner

OpenCL Lyra2REv2/v3 miner for AMD GCN GPUs
GNU General Public License v3.0
45 stars 19 forks source link

hash rate drop #11

Open oldskoolau opened 6 years ago

oldskoolau commented 6 years ago

im not sure if its just my setup

here is my setup 2x rx480 drivers 18.6.1 hash rate 74.60 system 1 2 rx vega 64 drivers 17.11.1 hash rate 154.40 system 2

have tried muliple pools same result after 1 to 3 days my pool the hash rat will drop the lowest was 4 mhs miner still tells me in mining at the above rates but pool rates are basically non existant i tied updating the drivers on the 480s no change lokking at the pool graphs you can see the rate declince and where i restart it every time

also noticesed each card keeps having differnt work loads card 1 will be 512 then card 2 will be 32 or 1024 and 128 all settings are the same for both cards im not sure if im missing something i have tried the recomended setting in the read me same result on all

hope there is enough info to go on if not will provide any thing required

thanks in advance

CryptoGraphics commented 6 years ago

Hello.

  1. Make sure that configuration file matches your physical devices, e.g generate it again and compare with original one.

  2. Since there are 2(even) number of devices and they are the same. Make sure that WorkSize value is also the same. Note: When miner starts, depending on your WorkSize parameter, these values should be also the same. (e.g, if WorkSize = 1048576)

    Device: 0 max runs: 2048
    Device: 1 max runs: 2048
  3. These lines should appear during mining.

    Device: 0 has completed its nonce range
    Device: 1 has completed its nonce range

    They indicate that specific Devices(GPUs) have completed all "runs"(e.g 2048).

  4. Make sure that all GPUs have 100% load. Actual per device hash-rate is(e.g) Device #0: 62.91 MH, 28.50 MH/s

Note, currently global hash rate such as this one Accepted 5/5 (100%), 163.96 MH, 56.20 MH/s gets updated only when solution was found or Device: X has completed its nonce range. If 1 of the devices accidentally stops working(driver crashes, etc), then global hash rate will not be updated for it and the latest available information will be used instead.