mirror of
https://github.com/JayDDee/cpuminer-opt.git
synced 2025-09-17 23:44:27 +00:00
Updated Home (markdown)
75
Home.md
75
Home.md
@@ -412,23 +412,94 @@ The startup messages are very important to ensure best performmance. In particul
|
||||
the features lists ensure the software is built for the CPU architecture and can
|
||||
take advantage of all the algo optimizations.
|
||||
|
||||
`
|
||||
CPU: AMD Ryzen 7 1700 Eight-Core Processor .
|
||||
SW built on Feb 7 2020 with GCC 7.4.0.
|
||||
CPU features: AVX2 AES SHA
|
||||
SW features: AVX2 AES SHA
|
||||
Algo features: AVX512
|
||||
|
||||
Starting miner with AVX2...
|
||||
`
|
||||
|
||||
|
||||
|
||||
### New stratum, block job report
|
||||
|
||||
This report is issued when a new job is received from the stratum server.
|
||||
If the report is also for a new block or a changed stratum difficulty the report
|
||||
will include new estimates for the new block or stratum difficulty.
|
||||
|
||||
`
|
||||
[2020-02-07 23:38:22] New block 1293839, job 1d9f
|
||||
lyra2rev3: lyra2v3.mine.zergpool.com:4550
|
||||
Diff: Net 50648, Stratum 26, Target 0.10156
|
||||
TTF @ 2758.00 kh/s: block 2y2d, share 2m38s
|
||||
Net TTF @ 1040.82 Gh/s: 3m29s
|
||||
`
|
||||
There are 3 forms of this report. New job is a one line report, new block and new stratum diff are up to
|
||||
4 lines. A new stratum diff also includes a new block and a new block includes a new job.
|
||||
|
||||
Line 1 (blue) shows what new information was received from the stratum server.
|
||||
|
||||
Line 2 shows the current algo anf pool URL.
|
||||
|
||||
Line 3:
|
||||
* Network difficulty
|
||||
* Stratum difficulty, provide by the server
|
||||
* Target difficulty, the minimum acceptible share difficulty, calculated from data received from the stratum
|
||||
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.
|
||||
* Reference hash rate of the miner, calculated by counting the number of hashes over time.
|
||||
* Block TTF
|
||||
* Share TTF
|
||||
|
||||
Line 5, only displayed in single coin pools, shows the network hashrate and the network block TTF.
|
||||
|
||||
### Share submitted report
|
||||
|
||||
The main purpose of this report is to timestamp when a share is submitted
|
||||
and record the job id for later comparison with the share result.
|
||||
`
|
||||
[2020-02-07 23:59:03] 5 submitted by thread 15, lane 1, job 1dd6
|
||||
`
|
||||
The main purpose of the share submitted report is to timestamp the event to meaure latency.
|
||||
|
||||
The first number is a simple counter that is incremented every time a share is submitted. It should always
|
||||
match up with a share result.
|
||||
|
||||
The CPU thread and lane are FYI. The lane is only displayed when hashing multiple data streams in parallel
|
||||
in each CPU thread.
|
||||
|
||||
The job id is displayed to help diagnose stale shares caused by latency.
|
||||
|
||||
### Share result report
|
||||
|
||||
This report is generated when a reply to a submitted share is received.
|
||||
|
||||
`
|
||||
[2020-02-07 23:59:03] 5 Accepted 5 S0 R0 B0, 400.092 sec (159ms)
|
||||
Diff 0.11393 (0.0853%), Block 1044635, Job 1dd6
|
||||
`
|
||||
Line 1:
|
||||
* Share result counter, should match share submitted counter.
|
||||
* Accepted share count. If thecurrent share was accepted, as in the example, The initial is expanded
|
||||
into the full word and is coloured green. If the curent shar ewas not accepted is the count is displated
|
||||
in its abbreviated form: A5.
|
||||
* Stale share count, coloured and expanded to "Stale job" and coloured yellow if the current share is state.
|
||||
* Rejected share count, coloured red.
|
||||
* Solved block count, with "BLOCK SOLVED" coloured magenta. A solved block also counts as an accepted share
|
||||
incrementing the accepted count and colouring it green.
|
||||
* The time in seconds since the last share followed by (latency).
|
||||
|
||||
Line2:
|
||||
* Share difficulty. The share difficulty does matter most of the time as long as it is higher or equal to the target difficulty as all shares are considered equal by the pool server.
|
||||
* (share ratio %) the percentage of the difficulty required to find a block.
|
||||
* The height of the current block, 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
|
||||
|
||||
Generated aproximately every 5 miinutes. It is not precise because it is an opportunistic report.
|
||||
|
Reference in New Issue
Block a user