Taking AWS monero mining notes:
c4.8xlarge
c4.8xlarge = 734 H/s w/ 36 threads
c4.8xlarge = 959 H/s w/ 24 threads
c4.8xlarge = 979 H/s w/ 25 threads
c4.8xlarge = 941 H/s w/ 26 threads
Verdict: L3 cache via lscpu is the best. Not profitable even with spot instance pricing.
r4.4xlarge
r4.4xlarge = 530 H/s w/ 15 threads
r4.4xlarge = 560 H/s w/ 16 threads
r4.4xlarge = 560 H/s w/ 17 threads
r4.4xlarge = 558 H/s w/ 18 threads
r4.4xlarge = 525 H/s w/ 24 threads
r4.2xlarge
r4.2xlarge = 287 H/s w/ 8 threads
r4.2xlarge = 300 H/s w/ 9 threads
r4.2xlarge = 290 H/s w/ 10 threads
r4.2xlarge = 284 H/s w/ 16 threads
The numbers are jumping quite a bit on all of the AWS instances. Likely due to resource contention. All instances launched on E5-2686 V4 machines.
c4.8xlarge
c4.8xlarge = 734 H/s w/ 36 threads
c4.8xlarge = 959 H/s w/ 24 threads
c4.8xlarge = 979 H/s w/ 25 threads
c4.8xlarge = 941 H/s w/ 26 threads
Verdict: L3 cache via lscpu is the best. Not profitable even with spot instance pricing.
r4.4xlarge
r4.4xlarge = 530 H/s w/ 15 threads
r4.4xlarge = 560 H/s w/ 16 threads
r4.4xlarge = 560 H/s w/ 17 threads
r4.4xlarge = 558 H/s w/ 18 threads
r4.4xlarge = 525 H/s w/ 24 threads
r4.2xlarge
r4.2xlarge = 287 H/s w/ 8 threads
r4.2xlarge = 300 H/s w/ 9 threads
r4.2xlarge = 290 H/s w/ 10 threads
r4.2xlarge = 284 H/s w/ 16 threads
The numbers are jumping quite a bit on all of the AWS instances. Likely due to resource contention. All instances launched on E5-2686 V4 machines.
Last edited: