SCRYPT-README 4.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131
  1. If you wish to donate to the author of scrypt support, Con Kolivas, please send
  2. your donations to:
  3. Bitcoin : 15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ
  4. Litecoin: Lc8TWMiKM7gRUrG8VB8pPNP1Yvt1SGZnoH
  5. ---
  6. Scrypt mining for GPU is completely different to sha256 used for bitcoin
  7. mining. It has very different requirements to bitcoin mining and is a
  8. lot more complicated to get working well. Note that it is a ram dependent
  9. workload, and requires you to have enough system ram as well as fast enough
  10. GPU ram.
  11. There are 5 main parameters to tuning scrypt, 2 of which you MUST set, and
  12. the others are optional for further fine tuning. When you start scrypt mining
  13. with the --scrypt option, BFGMiner will fail IN RANDOM WAYS. They are all due
  14. to parameters being outside what the GPU can cope with. Not giving BFGMiner a
  15. hint as to your GPU type, it will hardly ever perform well.
  16. Step 1 on linux:
  17. export GPU_MAX_ALLOC_PERCENT=100
  18. If you do not do this, you may find it impossible to scrypt mine. You may find
  19. a value of 40 is enough and increasing this further has little effect.
  20. export GPU_USE_SYNC_OBJECTS=1
  21. may help CPU usage a little as well.
  22. --shaders XXX
  23. is a new option where you tell BFGMiner how many shaders your GPU has. This
  24. helps BFGMiner try to choose some meaningful baseline parameters. Use this table
  25. below to determine how many shaders your GPU has, and note that there are some
  26. variants of these cards, and nvidia shaders are much much lower and virtually
  27. pointless trying to mine on.
  28. GPU Shaders
  29. 7750 512
  30. 7770 640
  31. 7850 1024
  32. 7870 1280
  33. 7950 1792
  34. 7970 2048
  35. 6850 960
  36. 6870 1120
  37. 6950 1408
  38. 6970 1536
  39. 6990 (6970x2)
  40. 6570 480
  41. 6670 480
  42. 6790 800
  43. 6450 160
  44. 5670 400
  45. 5750 720
  46. 5770 800
  47. 5830 1120
  48. 5850 1440
  49. 5870 1600
  50. 5970 (5870x2)
  51. These are only used as a rough guide for BFGMiner, and it is rare that this is
  52. all you will need to set.
  53. --intensity XX
  54. Just like in bitcoin mining, scrypt mining takes an intensity, however the
  55. scale goes from 0 to 20 to mimic the "Aggression" used in mtrlt's reaper. The
  56. reason this is crucial is that too high an intensity can actually be
  57. disastrous with scrypt because it CAN run out of ram. Intensities over 13
  58. start writing over the same ram and it is highly dependent on the GPU, but they
  59. can start actually DECREASING your hashrate, or even worse, start producing
  60. garbage with rejects skyrocketing.
  61. Optional parameters to tune:
  62. -g, --thread-concurrency, --lookup-gap
  63. -g:
  64. Once you have found the optimal shaders and intensity, you can start increasing
  65. the -g value till BFGMiner fails to start. Rarely will you be able to go over
  66. about -g 4 and each increase in -g only increases hashrate slightly.
  67. --thread-concurrency:
  68. This tunes the optimal size of work that scrypt can do. It is internally tuned
  69. by BFGMiner to be the highest reasonable multiple of shaders that it can
  70. allocate on your GPU. Ideally it should be a multiple of your shader count.
  71. vliw5 architecture (R5XXX) would be best at 5x shaders, while VLIW4 (R6xxx and
  72. R7xxx) are best at 4x. Setting thread concurrency overrides anything you put
  73. into --shaders.
  74. --lookup-gap
  75. This tunes a compromise between ram usage and performance. Performance peaks
  76. at a gap of 2, but increasing the gap can save you some GPU ram, but almost
  77. always at the cost of significant loss of hashrate. Setting lookup gap
  78. overrides the default of 2, but BFGMiner will use the --shaders value to choose
  79. a thread-concurrency if you haven't chosen one.
  80. Overclocking for scrypt mining:
  81. First of all, do not underclock your memory initially. Scrypt mining requires
  82. memory speed and on most, but not all, GPUs, lowering memory speed lowers
  83. mining performance.
  84. Second, absolute engine clock speeds do NOT correlate with hashrate. The ratio
  85. of engine clock speed to memory matters, so if you set your memory to the
  86. default value, and then start overclocking as you are running it, you should
  87. find a sweet spot where the hashrate peaks and then it might actually drop if
  88. you increase the engine clock speed further. Unless you wish to run with a
  89. dynamic intensity, do not go over 13 without testing it while it's running to
  90. see that it increases hashrate AND utility WITHOUT increasing your rejects.
  91. Suggested values for 7970 for example:
  92. export GPU_MAX_ALLOC_PERCENT=100
  93. --shaders 2048 -g 5 --gpu-engine 1135 --gpu-memclock 1375
  94. ---
  95. If you wish to donate to the author of scrypt support, Con Kolivas, please send
  96. your donations to:
  97. Bitcoin : 15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ
  98. Litecoin: Lc8TWMiKM7gRUrG8VB8pPNP1Yvt1SGZnoH