Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.8 (Windows/Linux)
by
scryptr
on 12/08/2017, 11:29:17 UTC
Anyone have experience with altering the ETH intensity?


-ethi   Ethereum intensity. Default value is 8, you can decrease this value if you don't want Windows to freeze or if you have problems with stability. The most low GPU load is "-ethi 0".
   Also "-ethi" now can set intensity for every card individually, for example "-ethi 1,8,6".
   You can also specify negative values, for example, "-ethi -8192", it exactly means "global work size" parameter which is used in official miner.


I understand that default is "8", and I also see that "0" is the lowest, but it does not mention the highest setting. I suppose that's when your system crashes or becomes unusable?

Is there a benefit to changing from default in your experiences?

The example above which discusses setting intensity for every card individually ("-ethi 1,8,6") --- Is the first number the desired intensity, and it applies that to cards 8 and 6? I just need a little clarification on that point.

THANKS

THE DEFAULT IS 8--

That is also the highest setting.  For individual cards, the syntax is often comma or space separated per card, depending on the mining software.  The value for GPU 0 is first, then comma, then for GPU 1, then comma, then GPU2... and so forth.  Claymore decided to use commas rather than spaces.  If you use a negative value, you are setting a "Global Work Size", as was used in the original Ethminer.  You could double, or perhaps quadruple that value, but I would not bother to use it.  Single digits (integers) from 0 to 8 are much easier to type.       --scryptr


Please do not put out wrong information. Or Knowingly lie to users.

PLEASE CORRECT ME--

I have not lied to anyone.       --scryptr


That is also the highest setting.

Max setting for ethi is 16

THANK YOU! --

Sorry, although I have read the README!!!.txt several times, it seems that I forgot an item.  Personally, I never bothered much with "-ethi", but was more concerned with "-dcri".

I fiddle with my rigs around the clock, and try to keep up-to-date with the threads, like this one.  If I answer someone I always try my best, but I missed this catch.  Apologies!!!  And, thank you for correcting me.  I had the sneeking suspicion that I should have checked the README!!!.txt before I posted, but it was late.   Haste makes waste.       --scryptr