Updated Home (markdown)

JayDDee
2020-02-19 00:43:42 -05:00
parent 2bda887cd4
commit d18becd5b6

57
Home.md

@@ -173,7 +173,7 @@ Local builds will always have the best performance and compatibility.
3. Download cpuminer-opt
------------------------
Download the source code for the latest realease from the official repository.
Download the source code for the latest release from the official repository.
https://github.com/JayDDee/cpuminer-opt/releases
@@ -428,26 +428,26 @@ Line 4: Extensions supported, to varying degrees, by the mining algorithm
Line 5: Extensions to be used in the current session
Hardware extensions are divided into 3 classes, SIMD, AES and SHA. There are multiple levels in each clash.
Each provides additional CPU instructions more complex operations.
Each provides additional CPU instructions and more complex operations.
* Simd vector support
* SIMD vector support
SSE2: minimum for 128 bit integer vector support, first available on Intel core2.
SSSE3: Some additional instructions for 128 bit integer vectors, not very significant.
SSE4.2: More 128 bit vector instructions, also not very significant.
AVX: Initial support for 256 bit vectors but no interger support.
AVX2: minimum level for 256 bit integer vector support, first available on Intel Haswell.
AVX: Initial support for 256 bit vectors but no integer support.
AVX2: minimum level for 256 bit integer vector support, first available on Intel Haswell amd AMD Ryzen.
AVX512: a suite of seperate extensions that provide 512 bit integer vector support, first available on
Intel Cascade Lake X HEDT CPUs.
* AES encryption and decryption, aka AES_NI
AES: basic hardware AES support performs AES operations with a single instruction, also requires SSE2,
first available on Intel Westmere.
VAES: vectored AES, supports 4 parallel AES operation with a single instruction, first available on Intel
VAES: Vectored AES, supports 4 parallel AES operations with a single instruction, first available on Intel
Icelake.
* SHA encryption and decryption, aka SHA_NI
SHA supports basic SHA-256 operations with a single instruction, also requires SSE2. First available
on Intel Goldont but not widely avaiable until AMD Ryzen and Intel Icelake.
on Intel Goldmont but not widely avaiable until AMD Ryzen and Intel Icelake.
### New stratum, block job report
@@ -481,12 +481,12 @@ server.
Line 4:
* TTF, an abbeviation for Time To Find, an estimate of the average time required to find either a block or a share for the miner.
* TTF, an abbeviation for Time To Find, an estimate of the average time required to find either a block or a share for a given hash rate.
* Reference hash rate of the miner, calculated by counting the number of hashes over time.
* Block TTF estimate calculated from miner's reference hashrate and network difficulty.
* Share TTF estimate calculated from miner's refence hash rate and target difficulty.
* Share TTF estimate calculated from miner's reference hash rate and target difficulty.
Line 5, experimental, only displayed in single coin pools
Line 5, only displayed in single coin pools
* network hashrate estimate calculated from network difficulty and the number of blocks found during
the session.
@@ -525,32 +525,45 @@ Line 1:
* Share result count, simple counter independant of submit counter but they should match. a mismatch indicates
submitted shares without replies. the result count should also equal the sum of accepted, stale and rejected
shares, collectivley know as replied or acknowledged shares.
* Accepted, Stale job, Rejected, BLOCK SOLVED counters. The currently incremented counter is coloured green
if accepted, yellow if stale, red if rejected, magenta if block solved. The other counters will be displayed
in their short form with no colouring. Solved blocks also count as accepted therefore the accepted count with
also be incremented and displayed in green in abbreviated form. The block count will be displayed in mmagenta
in long form.
shares, collectivley known as replied or acknowledged shares.
* "Accepted", "Stale", "Rejected", "BLOCK SOLVED" counters. The currently incremented counter is coloured green
if accepted, yellow if stale, red if rejected, magenta if it solved a block. The other counters will be
displayed in their short form with no colouring. Solved blocks also count as accepted therefore the accepted
count with also be incremented and displayed in green in abbreviated form. The block count will be displayed
in mmagenta in long form.
* The time in seconds since the last share
* (Latency ms) Time from submission to reply including transmission time and processing at either end.
Line 2:
* Share difficulty. The share difficulty does ot matter most of the time so is FYI. As long as the share
difficultty it is higher than or equal to the target difficulty as all shares are considered equal by the
difficulty it is higher than or equal to the target difficulty all shares are considered equal by the
pool server based on the stratum difficulty.
* (share ratio %) the percentage of the difficulty required to find a block.
* (share ratio %) the percentage of the difficulty required to find a block, 100% or greater solves a block.
* The current block height, coloured magenta when the block is found by the miner.
* The id of the job used to submit the share, coloured yellow if the job was stale.
### Periodic summary report
`
[2020-02-18 23:50:16] Periodic Report 5m35s 5m35s
Share rate 0.36/min 0.36/min
Hash rate 1600.25kh/s 1602.60kh/s (1654.96kh/s)
Submitted 2 2
Accepted 2 2
`
Generated aproximately every 5 minutes. The timing is not precise because it is an opportunistic report.
It is produced when it is convenient in order to miminize the impact on mining.
The report contains data for the 5 minute interval as well as session statistics.
The report contains data for the 5 minute interval in the left column, and session statistics in the right.
* Line 1: Sample time for current period and session
* Line 2: Number of shares submitted per minute
* Line 3: Hash rate calculated from share rate and stratum difficulty
* Line 4: Numner of shares submitted.
* Lines 5+: Optional number of stale or rejected shares or solved blocks, only displayed if not zero.
### CPU temperature and frequency report
@@ -563,5 +576,5 @@ frequently at higher temperatures and colour coded.
In addition the report will in a shorter interval if the new temperature exceeds the previous maximum.
The sampling is approximately every 30 seconds. The reported maximum it the highest sample and does
not represent the actual instantaneous maximum temperature.
The sampling is approximately every 30 seconds. The reported maximum it the previous maximum temperature
prirt to the current sample and does not represent the actual instantaneous maximum temperature.