GOSTSec
/
sgminer
mirror of https://github.com/GOSTSec/sgminer
1
0
Fork 0
Code Issues Releases Wiki Activity
Browse Source

More scrypt intensity information.

nfactor-troky
Con Kolivas 12 years ago
parent
52821d4241
commit
4cf2b4da23
1 changed files with 4 additions and 1 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 5
      SCRYPT-README

5
SCRYPT-README
Unescape View File

@ -81,7 +81,10 @@ reason this is crucial is that too high an intensity can actually be
disastrous with scrypt because it CAN run out of ram. Intensities over 13 disastrous with scrypt because it CAN run out of ram. Intensities over 13
start writing over the same ram and it is highly dependent on the GPU, but they start writing over the same ram and it is highly dependent on the GPU, but they
can start actually DECREASING your hashrate, or even worse, start producing can start actually DECREASING your hashrate, or even worse, start producing
garbage with rejects skyrocketing. garbage with rejects skyrocketing. The low level detail is that intensity is
only guaranteed up to the power of 2 that most closely matches the thread
concurrency. i.e. a thread concurrency of 6144 has 8192 as the nearest power
of two above it, thus as 2^13=8192, that is an intensity of 13.
Optional parameters to tune: Optional parameters to tune:

Write Preview
Loading…
Cancel
Save