New CPU Miner Guide



  • This is a guide to help people understand the newest version of the CPU miner and to try and answer any questions you may have regarding what information is shown on the screen and also how to get the best performance from your machine(s) when using it. This is a screenshot of what the new miner looks like:

    0_1495121033859_new_miner_screenshot.png

    The output is very different from what most users of the previous miner are used to. Some aspects such as PPS are gone and it no longer shows each threads hash when a new block begins, and there are also new sets of information shown, such as the chain chart as well as extra information regarding sieving and testing performance. Below are brief explanations for each of the categories you will see when using the new miner.

    WPS - This is a measurement of work per second. It is a measurement of the amount of chains with a length of 3 or more the miner finds per second. This value is weighted based on the length of the chain, with longer chains being worth more. This is essentially the standard metric for performance of your miner. The higher this number, the more computing power your miner is using, and in turn, the more NXS you will earn. (There is more to it, this is just a very generalized statement. For details about earnings, please see FAQ below.)

    Largest Share - This is the difficulty value of the largest share the miner has found since it started running. This number is reset any time the miner is closed or restarted. It is most useful as a quick way of knowing whether you might have solved a block or not. For example if you see your largest share was a 7.96, like in the picture, and you know the difficulty isn't usually that high, there’s a good chance you solved a block. This is NOT a guarantee however, as your share may have ended up being an Orphan (Orphans are explained below in the FAQ).

    Diff. - This is the target difficulty for the current block. In order to solve a block you need to submit a share that is larger than the target difficulty. More details for how difficulty is calculated can be found in the FAQ below.

    Height - This is the block number the miner is currently working on.

    Balance - This is only visible when pool mining. This displays the current amount of coins that your NXS address has on the pool. *NOTE* THIS IS NOT THE SAME AS YOUR NXS BALANCE IN YOUR WALLET. Pools keep a separate balance and then pay out to your NXS wallet when the balance reaches a certain point. Details as to how this is done can be found below in the FAQ.

    Payout - This is also only visible when pool mining. This displays the amount of coins that is set to be sent to your NXS wallet when the pool solves the next block. This number is USUALLY equal to your balance, but sometimes will be only a portion of your balance. Details regarding pool balance/payout process can be found in the FAQ below.

    Block(s) ACC=0 REJ=0 - This is only visible when solo mining. This shows the amount of blocks you have submitted solutions for, whether they were accepted or rejected. Block solutions can be rejected for different reasons, usually due to someone else submitting a solution first and your solution being submitted afterwards before your miner updated and started working on next block. This results in what is called an 'Orphan'.

    00d-00:00:00 - This is the length of time in Days-Hours:Minutes:Seconds that the miner has been running. This value resets any time the miner is close and/or restarted.

    Chain chart:

    ch - This row lists the length of chains found, from 3 through 9. Information on what a chain is can be found in FAQ below.

    count - This row lists the number of initial primes your miner has found that have the chain length shown in the 'ch' column above.

    ch/m - This row lists the number of initial primes your miner finds per minute, on average, for each chain length shown in the 'ch' column above.

    ratio - This is the ratio, on average, of prime chains found of each length compared to the previous chain length. For example, if the ratio for 4ch is 10.000, that means for every 10 3ch primes the miner finds, it typically finds 1 4ch prime. If the ratio for 5ch is 21, then it averages 1 5ch prime for every 21 4ch primes if finds, etc etc. This is mostly useful when trying to see the effects when editing the miners settings to try and generate longer chains more often than shorter ones, but this is only recommended for advanced users as altering some settings in the miner.conf file can severely decrease your mining performance if you aren't careful.

    AVG Time Sieve - This is the average time, in microseconds (1/1,000,000th of a second) that each sieving thread starts sieving a new number. For example, if this number is 250000, each sieving thread will sieve out a new number every 0.25 seconds, or 4 times every second in other words.

    AVG Time PTest - This is the average time, in microseconds (1/1,000,000th of a second) that each PTest thread test 200 numbers found by the sieving threads. For example, if this number is 500000, each PTest thread will test 200 numbers to see if they are the beginning of a prime chain and, if so, how long the chain is. More details about chains/initial primes can be found in the FAQ below.

    Siv/s - This is how many sieves ALL of your sieving threads complete each second. This is determined by dividing the number of sieving threads you have by the AVG time each one takes to complete. For example, if you have 3 sieving threads and your AVG Time Sieve is 250000, you will complete a total of 12 sieves per second, on average.

    Tst/s - This is how many sets of 200 numbers ALL of your PTest threads test for chains each second. This is determined by dividing the number of PTest threads you have by the AVG time each one takes to complete. For example, if you have 6 PTest threads and your AVG Time PTest is 500000, you will complete 12 sets of tests per second, on average. *NOTE* This is most useful when setting your sieving/PTest threads in the miner.conf file. You want to make sure the Tst/s can keep up (will always be lower) with your Siv/s value. If they aren't close, you will begin building up more numbers than you're testing and will likely start to receive a warning in the miner. If this happens, you need to either increase your PTest threads, or decrease your sieving threads. More details for how to find best setup for your machine(s) can be found in FAQ below.

    Shares - This is only visible when pool mining. This is the number of initial primes your miner has found that had a difficulty value greater than 4.500000 (this minimum difficulty is set by the pool and can be different depending on what the pool administrator chooses). This is only a count, and doesn't reflect the actual value of each share, as longer chains are worth more to the pool.

    Shr/h - This is only visible when pool mining. This is the number of shares, on average, your miner finds per hour that meet the minimum difficulty requirement set by the pool. This is simply the amount of time the miner has been running divided by the number of Shares shown.

    TotalShareValue - This is only visible when pool mining. This is the value of all submitted shares, taking into consideration, their chain length. Longer chain shares are worth more than shorter length shares. This number is a running total since the miner started and does NOT reflect the share value for current round itself. More details regarding how values are calculated can be found in the FAQ below.

    ShrVal/h - This is only visible when pool mining. This is the average value of shares your miner submits per hour. *NOTE* This is the best indicator of the earning potential/performance of your miner!!! The higher this number, the larger your share will be from the block reward when the pool solves a block. This is an average, however, and various things can affect how much of the block reward you earn. Details regarding pool earnings and how they work can be found in the FAQ below.

    ***FAQ's can be found here***


Log in to reply
 

Looks like your connection to NXSForum.com was lost, please wait while we try to reconnect.