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

Update SCRYPT README with information about HW errors.

nfactor-troky
Con Kolivas 12 years ago
parent
e49bd98196
commit
b406dbfe78
1 changed files with 5 additions and 2 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. 7
      SCRYPT-README

7
SCRYPT-README
Unescape View File

@ -24,6 +24,9 @@ with the --scrypt option, cgminer will fail IN RANDOM WAYS. They are all due
to parameters being outside what the GPU can cope with. Not giving cgminer a to parameters being outside what the GPU can cope with. Not giving cgminer a
hint as to your GPU type, it will hardly ever perform well. hint as to your GPU type, it will hardly ever perform well.
NOTE that if it does not fail at startup, the presence of hardware errors (HW)
are a sure sign that you have set the parameters too high.
Step 1 on linux: Step 1 on linux:
export GPU_MAX_ALLOC_PERCENT=100 export GPU_MAX_ALLOC_PERCENT=100
@ -81,7 +84,7 @@ 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. The low level detail is that intensity is garbage with HW errors skyrocketing. The low level detail is that intensity is
only guaranteed up to the power of 2 that most closely matches the thread 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 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. of two above it, thus as 2^13=8192, that is an intensity of 13.
@ -122,7 +125,7 @@ default value, and then start overclocking as you are running it, you should
find a sweet spot where the hashrate peaks and then it might actually drop if find a sweet spot where the hashrate peaks and then it might actually drop if
you increase the engine clock speed further. Unless you wish to run with a you increase the engine clock speed further. Unless you wish to run with a
dynamic intensity, do not go over 13 without testing it while it's running to dynamic intensity, do not go over 13 without testing it while it's running to
see that it increases hashrate AND utility WITHOUT increasing your rejects. see that it increases hashrate AND utility WITHOUT increasing your HW errors.
Suggested values for 7970 for example: Suggested values for 7970 for example:

Write Preview
Loading…
Cancel
Save