Ke/s is actually the kilo-encryptions (thousands of encryptions) per second of mining power in PKT. The higher the Ke/s, the higher the rewards you earn from mining.
CPU type / clock CPU threads used OS Miner Observed Ke/s (average) Date of entry PKT/day** Pool Configuration AMD Ryzen 5 3600 / stock 12 Debian Buster (VM) packetcrypt_rs 610 July 13th, 2021 114.37500714844 AMD Ryzen 7 4800U / stock 16 Debian Buster (VM) packetcrypt_rs 650 July 13th, 2021 121.87500761719 AMD Ryzen 9 5900X / stock 24 Windows 10 packetcrypt.exe 1500 July 13th, 2021 281.25001757813 AMD Ryzen 9 5900X / stock 24 Windows 10 WSL 2000 July 13th, 2021 375.0000234375 AMD Ryzen 9 5950X / stock 31 Ubuntu 20.04 LTS PacketCrypt 2400 July 13th, 2021 450 Intel Core i7-4710HQ 8 WSL 350 July 13th, 2021 65.625004101563 Intel Core i7 10700K 16 Windows 10 packetcrypt_rs via WSL2 1300 July 15th, 2021 243.75001523438 AKASH Deployment 10 Unknown packetcrypt Unknown August 24th, 2021 82 Srizbi, Pktpool, Pktworld, Pkteer, Pktco AKASH Deployment 10 Unknown packetcrypt Unknown August 24th, 2021 65 Srizbi, Pktpool, Pktworld AKASH Deployment 6 Unknown packetcrypt Unknown August 24th, 2021 37 Srizbi
Mining PKT requires two types of superpower: CPU and bandwidth. The faster the CPU, and the bandwidth, the higher the PKT mining rewards would be.
As you know not all CPUs are created equal, some CPUs have higher computer power whereas the others don’t.
In PKT mining, CPU power is calculated based on Ke/s, not the number of cores and threads. Learn more about the best CPUs for PKT mining.
When you successful mine PKT, you get messages like this:
1618394538 INFO annmine.rs:519 1093 Ke/s 25.17Mb/s overflow: [2040, 0, 0192] uploading: [11264, 4096, 20400] accept/reject: [12200/0, 0/0, 13312/0, 0/0] – goodrate: [05%, 100%, 0%]
Let me break it down the information for easy understanding:
- 1093 Ke/s 1093 kilo-encryptions (thousands of encryptions) per second of mining power.
- 25.17 Mb/s Total upload bandwidth (to all pools – combined) overflow: [0, 0, 3072, 0] Overflowed the internal queue of the ann miner, before it was even able to upload to the pool, one number for each pool you’re mining to.
- 2040 Number of anns which are not uploaded to pool #3.
- uploading [11264, 4096, 20400] Number of anns currently in-flight in active http requests, again 3rd pool is a problem, others are doing well (in this example).
- accept/reject [12200/0, 0/0, 13312/0, 0/0] Anns accepted/rejected by each pool, these numbers are based on the previous 10 seconds, pool #2 is giving zero acceptance which might be an issue, keep watching the next message 10 seconds later for another update.
- goodrate [05%, 100%, 0%] Goodrate = number of anns accepted divided by number of anns produced.