From fca01794d27eb4215641ab2255d2f49687ced4e2 Mon Sep 17 00:00:00 2001 From: JayDDee Date: Sat, 8 Feb 2020 02:17:28 -0500 Subject: [PATCH] Updated Home (markdown) --- Home.md | 90 +++++++++++++++++++++++++++++++++++---------------------- 1 file changed, 55 insertions(+), 35 deletions(-) diff --git a/Home.md b/Home.md index 9b97d70..e17b2d2 100644 --- a/Home.md +++ b/Home.md @@ -412,7 +412,7 @@ 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 @@ -420,7 +420,7 @@ SW features: AVX2 AES SHA Algo features: AVX512 Starting miner with AVX2... -` + @@ -429,6 +429,7 @@ Starting miner with AVX2... 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. +Using external data the coin can be identifed from its block number. ` [2020-02-07 23:38:22] New block 1293839, job 1d9f @@ -437,86 +438,105 @@ will include new estimates for the new block or stratum difficulty. 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 2 shows the current algo and 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 +* 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. -Line 5, only displayed in single coin pools, shows the network hashrate and the network block TTF. +Line 5, experimental, only displayed in single coin pools + +* network hashrate estimate calculated from network difficulty and the number of blocks found during + the session. +* observed network block TTF calculated from the number of blocks found during the session. ### Share submitted report ` [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 main purpose of the share submitted report is to timestamp the event to measure latency. -The job id is displayed to help diagnose stale shares caused by latency. +* submit count is a simple counter that is incremented every time a share is submitted. It should always +match up with a share result counter. + +* CPU thread that submitted the share, FYI Only. + +* Lane of the CPU thread that submitted theshare, only displayed when hashing multiple data streams in + parallel (N way). FYI only. + +* 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. +This report is generated when the pool's reply has been received acknowledging the submitted share. ` [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. + +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. +* 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 +pool server based on the stratum difficulty. * (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 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 -Generated aproximately every 5 miinutes. It is not precise because it is an opportunistic report. +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. ### CPU temperature and frequency report -Another opportunistic report to avoid interrupting mining operation. In adition -the frequency of the report is dependent on the current temperature. +Another opportunistic report to avoid interrupting mining operation. Temperature reports are dsplayed more +frequently at higher temperatures and colour coded. -* temp > 80: 30 seconds -* 70 <= temp <= 80: 1 minute -* t < 70: 2 minutes +* temp > 80: 30 seconds, red +* 70 <= temp <= 80: 1 minute, yellow +* t < 70: 2 minutes, no colour -In addition the report will be generated sooner if the current temperature exceeds the previous maximum. +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 -not represent the actual instantaneous maximim temperature. \ No newline at end of file +The sampling is approximately every 30 seconds. The reported maximum it the highest sample and does +not represent the actual instantaneous maximum temperature. \ No newline at end of file