You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Spin up single instance of bitcoind (BCHN) and [ASICseer BCH pool] software on single server of approximately E3-1240 V2 @ 3.40GHz with 16GB of ram (or similar) using SSD storage
Have ASICseer ops point >= 50PH/s of SHA256 hashrate at the server for extended period of time (>3 hrs)
Verify <= 10% cpu load @ 50PH/s average over course of >3hrs
Verify acceptable RAM usage and availability @ >= 50PH/s
Check for overall system stability and mem/processing leaks
Expected Result
Listed device should comfortably handle >= 100PH/s as a bare minimum on [ASICseer BCH pool] software. Current p2pool codebase (with modifications) able to handle:
40PH/s (fully tweaked linux system) @ load average: 0.12, 0.09, 0.13 using 1.3GB ram
40PH/s p2pool average (~150 stratum connections): RX 27 KB/s and TX 737 KB/s with peaks: 762 KB/s RX and 2990 KB/s TX
The text was updated successfully, but these errors were encountered:
Environment
Devices: E3-1240 V2 @ 3.40GHz / 16GB ram / SSD storage
Steps to Reproduce
Expected Result
Listed device should comfortably handle >= 100PH/s as a bare minimum on [ASICseer BCH pool] software. Current p2pool codebase (with modifications) able to handle:
40PH/s (fully tweaked linux system) @ load average: 0.12, 0.09, 0.13 using 1.3GB ram
40PH/s p2pool average (~150 stratum connections): RX 27 KB/s and TX 737 KB/s with peaks: 762 KB/s RX and 2990 KB/s TX
The text was updated successfully, but these errors were encountered: