AEON Mining Performance

dwright1542

Active Member
Dec 26, 2015
362
69
28
47
Hey, Patrick,

If you ever get to it, I'd appreciate if you could re-run these Aeon numbers using my lukMiner release, too. You have quite a number of machines there for which I'd be curious to hear the hash rate for ...

Luk
If we can compile on Windows, I've got a bunch of machines that I can compare with xmrig.
 

Klee

Well-Known Member
Jun 2, 2016
1,285
393
83
Hey, Patrick,

If you ever get to it, I'd appreciate if you could re-run these Aeon numbers using my lukMiner release, too. You have quite a number of machines there for which I'd be curious to hear the hash rate for ...

Luk
Just a quick test.

First I have to give you information on my setup and particularly on my cpu's in my main workstation that ran this one test, they are E5-2667 V3 ES cpu's with 35 MB L3 each. They are apparently 14 core cpu's that Intel disabled all but 8 cores each explaining the large L3. Base clock is 2.9 Ghz and all core boost is 3.0 Ghz. This is on a Asrock Rack EP2C612 WS dual cpu motherboard. 64 Gigs of Trident Z ram.

Running xmrig using all 32 cores using one instance, not optimizing for numa nodes by using two instances.

Xmrig shows only 1 cpu but it does uses all 32 cores.

I edited out the private pool address I use and some of the output to make this post shorter.

me@LinuxBeast:~/miners/aeon-xmrig/build$ ./xmrig
* VERSIONS: XMRig/2.3.1 libuv/1.9.1 gcc/6.3.0
* HUGE PAGES: available, enabled
* CPU: Genuine Intel(R) CPU @ 2.90GHz (1) x64 AES-NI
* CPU L2/L3: 3.5 MB/35.0 MB
* THREADS: 32, cryptonight-lite, av=2, donate=1%
* POOL #1: :4334
* COMMANDS: hashrate, pause, resume
[2017-11-25 22:31:42] use pool
[2017-11-25 22:31:42] new job from :4334 diff 20000
[2017-11-25 22:31:44] accepted (1/0) diff 20000 (109 ms)
[2017-11-25 22:31:46] accepted (2/0) diff 20000 (109 ms)
[2017-11-25 22:31:50] accepted (3/0) diff 20000 (111 ms)
[2017-11-25 22:31:54] new job from :4334 diff 30000
[2017-11-25 22:32:06] speed 2.5s/60s/15m 4164.5 n/a n/a H/s max: 4246.9 H/s
[2017-11-25 22:32:13] accepted (4/0) diff 30000 (109 ms)
[2017-11-25 22:32:14] accepted (5/0) diff 30000 (108 ms)
[2017-11-25 22:32:15] accepted (6/0) diff 30000 (109 ms)
[2017-11-25 22:32:24] new job from :4334 diff 45000
[2017-11-25 22:32:26] speed 2.5s/60s/15m 4231.7 n/a n/a H/s max: 4246.9 H/s
[2017-11-25 22:32:32] accepted (7/0) diff 45000 (108 ms)
[2017-11-25 22:32:37] accepted (8/0) diff 45000 (167 ms)
[2017-11-25 22:32:43] accepted (9/0) diff 45000 (109 ms)
[2017-11-25 22:32:46] speed 2.5s/60s/15m 3905.5 4077.0 n/a H/s max: 4246.9 H/s
[2017-11-25 22:32:53] accepted (10/0) diff 45000 (109 ms)
[2017-11-25 22:32:54] new job from :4334 diff 67500
[2017-11-25 22:33:03] new job from :4334 diff 67500
[2017-11-25 22:33:06] speed 2.5s/60s/15m 3787.2 4079.3 n/a H/s max: 4246.9 H/s
[2017-11-25 22:33:26] speed 2.5s/60s/15m 3948.7 3993.5 n/a H/s max: 4246.9 H/s
[2017-11-25 22:33:44] accepted (11/0) diff 67500 (109 ms)
[2017-11-25 22:33:46] speed 2.5s/60s/15m 3982.5 4020.3 n/a H/s max: 4246.9 H/s
[2017-11-25 22:33:54] new job from :4334 diff 100001
[2017-11-25 22:33:58] new job from :4334 diff 100001
[2017-11-25 22:34:06] speed 2.5s/60s/15m 3828.3 3959.2 n/a H/s max: 4246.9 H/s
[2017-11-25 22:34:16] accepted (12/0) diff 100001 (90 ms)
[2017-11-25 22:34:17] accepted (13/0) diff 100001 (75 ms)
[2017-11-25 22:34:26] speed 2.5s/60s/15m 4013.3 3964.3 n/a H/s max: 4246.9 H/s
[2017-11-25 22:34:30] new job from :4334 diff 100001
[2017-11-25 22:34:46] speed 2.5s/60s/15m 3908.8 3979.8 n/a H/s max: 4254.5 H/s
[2017-11-25 22:34:47] accepted (14/0) diff 100001 (112 ms)
[2017-11-25 22:34:57] Ctrl+C received, exiting
[2017-11-25 22:34:57] no active pools, stop mining

Now the output from lukminer:

me@LinuxBeast:~/Downloads/luk-miner$ bash luk-aeon.sh
luk-aeon.sh: line 45: /proc/sys/vm/nr_hugepages: Permission denied
----------- re-starting miner -----------
[22:24:47] ##################################################################
[22:24:47] # this is lukMiner v0.8.4 (for Aeon), starting up #
[22:24:47] # Release Notes: #
[22:24:47] # - this version is tested w/ minergate, dwarfpool, and my own #
[22:24:47] # stratum pool, as well as on AWS, GCE, and any CPU from #
[22:24:47] # YorkTown to SkyLake, and even Xeon Phi 72xx Knights Landing #
[22:24:47] # - opencl/gpu mining supported via the lukMinerCL binary #
[22:24:47] # (separate binary to avoid link dependency on main lukMiner) #
[22:24:47] # - latest updates: lukMiner - A New Cross-Platform Monero (XMR) and Aeon Miner #
[22:24:47] ##################################################################
[22:24:47] found 2 sockets, with 8 cores/socket, and 2 threads/core
[22:24:47] found caches of 256K level-1, 2M level-2, and 35M level-3 per socket
[22:24:47] CPU does seem to have AES-NI instructions ... perfect!
[22:24:47] using pool: :4334
[22:24:47] using user: Wmtmxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:x
[22:24:47] running config: 0x0201
[22:24:47] targeted developer share is 1%
[22:24:47] *******************************************************
[22:24:47] WARNING - you're mining aeon coins, but your pool's URL
[22:24:47] does not contain the string 'aeon' ... which often
[22:24:47] means you're trying to mine XMR coins on an AEON pool
[22:24:47] (or vice versa). After a brief pause I'll do what you
[22:24:47] asked me to, but you might want to double-check your
[22:24:47] URL (most pools will 'punish' you for invalid shares!)
[22:24:47] *******************************************************
[22:24:50] adding creator account (on dwarfpool)....
[22:24:50] connecting to pool :4334
[22:24:50] connecting to pool mine.aeon-pool.com:8080
[22:24:50] Starting watch-dog thread, with check interval 300 seconds
[22:24:50] at least one huge-page alloc was successful
[22:24:50] connection to pool created, socket ID 4
[22:24:50] (re?-)sending login request (for account #0: user Wmtmxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, pool :4334) ...
[22:24:50] connection to pool created, socket ID 5
[22:24:50] (re?-)sending login request (for account #1: user WmtNwQw3Lsr34SxvgmpkmbgirMRxDKCAKVkB7X9YmMKm3P5pfLQRv5tMfEQtXk7MiHU4WyN3Eakg2Mvbe26eXSkP2H14HmQxd, pool mine.aeon-pool.com:8080) ...
[22:25:03] thread 24: share FOUND (context 0, nonce 0x00770634)! (hash rate this thread = 133.809H/s)
[22:25:03] submitting share w/ difficulty 20000
[22:25:03] share ***accepted*** - yay!
[22:25:03] -> share accepted: 1/1 (100.00%) - total hashrate 4137.84H/s (may take a while to converge)
[22:25:05] new job at difficulty 30000.1
[22:25:07] thread 26: share FOUND (context 0, nonce 0x00030E6E)! (hash rate this thread = 137.343H/s)
[22:25:07] submitting share w/ difficulty 30000
[22:25:08] share ***accepted*** - yay!
[22:25:08] -> share accepted: 2/2 (100.00%) - total hashrate 4162.32H/s (may take a while to converge)
[22:25:11] thread 14: share FOUND (context 0, nonce 0x0039FE4C)! (hash rate this thread = 124.921H/s)
[22:25:11] submitting share w/ difficulty 30000
[22:25:11] share ***accepted*** - yay!
[22:25:11] -> share accepted: 3/3 (100.00%) - total hashrate 4142.67H/s (may take a while to converge)
[22:25:17] thread 24: share FOUND (context 1, nonce 0x007705EB)! (hash rate this thread = 136.868H/s)
[22:25:17] submitting share w/ difficulty 30000
[22:25:18] share ***accepted*** - yay!
[22:25:18] -> share accepted: 4/4 (100.00%) - total hashrate 4140.96H/s (may take a while to converge)
[22:25:25] thread 6: share FOUND (context 1, nonce 0x009BA869)! (hash rate this thread = 128.592H/s)
[22:25:25] submitting share w/ difficulty 30000
[22:25:25] share ***accepted*** - yay!
[22:25:25] -> share accepted: 5/5 (100.00%) - total hashrate 4096.54H/s (may take a while to converge)
[22:25:29] thread 24: share FOUND (context 1, nonce 0x00C35229)! (hash rate this thread = 128.598H/s)
[22:25:29] submitting share w/ difficulty 30000
[22:25:29] share ***accepted*** - yay!
[22:25:29] -> share accepted: 6/6 (100.00%) - total hashrate 4091.20H/s (may take a while to converge)
[22:25:30] *** total hash rate: 4088H/s (may take a while to converge)
[22:25:32] thread 25: share FOUND (context 1, nonce 0x00DBBDA9)! (hash rate this thread = 134.273H/s)
[22:25:32] submitting share w/ difficulty 30000
[22:25:32] share ***accepted*** - yay!
[22:25:32] -> share accepted: 7/7 (100.00%) - total hashrate 4040.59H/s (may take a while to converge)
[22:25:35] new job at difficulty 45000.3
[22:25:37] thread 27: share FOUND (context 1, nonce 0x0021926F)! (hash rate this thread = 133.755H/s)
[22:25:37] submitting share w/ difficulty 45000
[22:25:37] share ***accepted*** - yay!
[22:25:37] -> share accepted: 8/8 (100.00%) - total hashrate 4071.65H/s (may take a while to converge)
[22:25:43] thread 24: share FOUND (context 1, nonce 0x002DCAFD)! (hash rate this thread = 134.009H/s)
[22:25:43] submitting share w/ difficulty 45000
[22:25:43] share ***accepted*** - yay!
[22:25:43] -> share accepted: 9/9 (100.00%) - total hashrate 4095.61H/s (may take a while to converge)
[22:25:50] *** total hash rate: 4111H/s (may take a while to converge)
[22:25:55] new job at difficulty 9375.02
[22:26:00] thread 22: share FOUND (context 0, nonce 0x010368B2)! (hash rate this thread = 130.809H/s)
[22:26:00] submitting share w/ difficulty 45000
[22:26:00] share ***accepted*** - yay!
[22:26:00] -> share accepted: 10/10 (100.00%) - total hashrate 4179.12H/s (may take a while to converge)
[22:26:00] thread 0: share FOUND (context 0, nonce 0x0109834E)! (hash rate this thread = 128.379H/s)
[22:26:00] submitting share w/ difficulty 45000
[22:26:01] share ***accepted*** - yay!
[22:26:01] -> share accepted: 11/11 (100.00%) - total hashrate 4178.88H/s (may take a while to converge)
[22:26:05] new job at difficulty 67500.2
[22:26:10] *** total hash rate: 4187H/s (may take a while to converge)
[22:26:15] thread 10: share FOUND (context 0, nonce 0x00186F66)! (hash rate this thread = 135.804H/s)
[22:26:15] submitting share w/ difficulty 67500
[22:26:15] share ***accepted*** - yay!
[22:26:15] -> share accepted: 12/12 (100.00%) - total hashrate 4194.48H/s (may take a while to converge)
[22:26:30] *** total hash rate: 4132H/s (may take a while to converge)
[22:26:35] new job at difficulty 100002
[22:26:37] thread 22: share FOUND (context 0, nonce 0x00030DEE)! (hash rate this thread = 132.353H/s)
[22:26:37] submitting share w/ difficulty 9375
[22:26:37] share ***accepted*** - yay!
[22:26:37] -> share accepted: 13/13 (100.00%) - total hashrate 4098.47H/s (may take a while to converge)
[22:26:45] thread 8: share FOUND (context 0, nonce 0x00061A90)! (hash rate this thread = 130.663H/s)
[22:26:45] submitting share w/ difficulty 9375
[22:26:46] share ***accepted*** - yay!
[22:26:46] -> share accepted: 14/14 (100.00%) - total hashrate 4126.78H/s (may take a while to converge)
[22:26:50] *** total hash rate: 4137H/s (may take a while to converge)
[22:27:03] thread 2: share FOUND (context 1, nonce 0x0112AC15)! (hash rate this thread = 126.737H/s)
[22:27:03] submitting share w/ difficulty 100001
[22:27:03] share ***accepted*** - yay!
[22:27:03] -> share accepted: 15/15 (100.00%) - total hashrate 4192.30H/s (may take a while to converge)
[22:27:10] *** total hash rate: 4154H/s (may take a while to converge)
[22:27:30] *** total hash rate: 4128H/s (may take a while to converge)
[22:27:34] thread 30: share FOUND (context 0, nonce 0x0213054C)! (hash rate this thread = 123.645H/s)
[22:27:34] submitting share w/ difficulty 100001
[22:27:34] share ***accepted*** - yay!
[22:27:34] -> share accepted: 16/16 (100.00%) - total hashrate 4148.87H/s (may take a while to converge)
[22:27:50] *** total hash rate: 4176H/s (may take a while to converge)
[22:27:53] thread 7: share FOUND (context 1, nonce 0x02EBB1F9)! (hash rate this thread = 132.434H/s)
[22:27:53] submitting share w/ difficulty 100001
[22:27:53] share ***accepted*** - yay!
[22:27:53] -> share accepted: 17/17 (100.00%) - total hashrate 4215.88H/s (may take a while to converge)



Things I noticed:
Speed is comparable to xmrig, but since I did not optimize xmrig for numa nodes it is less consistent than your miner.

I see it handles the numa nodes properly. The %1 fee is fair. Needs more color not simply because it would look better but that the way xmrig displays the hash rate with a blue color and some of the other info with white makes it easier to see the important stuff at a glance.

I use a single dual E5-2620 server sometimes to monitor all my mining nodes vis ssh terminals and with six or more windows open it just makes it easier to see with multiple colors.

It being closed source binarys some will just not use it.

Xmrig does not handle numa nodes, supposed to be fixed in the future tho, so to get the highest speed you have to run one instance per numa node and with the new AMD cpu's that is a pain but yours seem to do great with the numa nodes on this pc.

This line in the config file "echo 10000 > /proc/sys/vm/nr_hugepages" would be an issue for most having to run the .sh using sudo to not have the error below. It runs fine on my setup but I do not know about setups that have not enabled hugepages already.

"luk-aeon.sh: line 45: /proc/sys/vm/nr_hugepages: Permission denied"

I already have hugepages enabled in the /etc/sysctl.conf file.

vm.nr_hugepages = 256.

So I commented out that line in the config file.

"# echo 10000 > /proc/sys/vm/nr_hugepages"

Then reran lukminer.

me@LinuxBeast:~/Downloads/luk-miner$ bash luk-aeon.sh
----------- re-starting miner -----------
[23:12:37] ##################################################################
[23:12:37] # this is lukMiner v0.8.4 (for Aeon), starting up #
[23:12:37] # Release Notes: #
[23:12:37] # - this version is tested w/ minergate, dwarfpool, and my own #
[23:12:37] # stratum pool, as well as on AWS, GCE, and any CPU from #
[23:12:37] # YorkTown to SkyLake, and even Xeon Phi 72xx Knights Landing #
[23:12:37] # - opencl/gpu mining supported via the lukMinerCL binary #
[23:12:37] # (separate binary to avoid link dependency on main lukMiner) #
[23:12:37] # - latest updates: lukMiner - A New Cross-Platform Monero (XMR) and Aeon Miner #
[23:12:37] ##################################################################
[23:12:37] found 2 sockets, with 8 cores/socket, and 2 threads/core
[23:12:37] found caches of 256K level-1, 2M level-2, and 35M level-3 per socket
[23:12:37] CPU does seem to have AES-NI instructions ... perfect!
[23:12:37] using pool: :4334
[23:12:37] using user: Wmtmxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:x
[23:12:37] running config: 0x0201
[23:12:37] targeted developer share is 1%
[23:12:37] *******************************************************
[23:12:37] WARNING - you're mining aeon coins, but your pool's URL
[23:12:37] does not contain the string 'aeon' ... which often
[23:12:37] means you're trying to mine XMR coins on an AEON pool
[23:12:37] (or vice versa). After a brief pause I'll do what you
[23:12:37] asked me to, but you might want to double-check your
[23:12:37] URL (most pools will 'punish' you for invalid shares!)
[23:12:37] *******************************************************
[23:12:40] adding creator account (on dwarfpool)....
[23:12:40] connecting to pool :4334
[23:12:40] connecting to pool mine.aeon-pool.com:8080
[23:12:40] Starting watch-dog thread, with check interval 300 seconds
[23:12:40] at least one huge-page alloc was successful
[23:12:40] connection to pool created, socket ID 4
[23:12:40] (re?-)sending login request (for account #0: user Wmtmxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, pool :4334) ...
[23:12:40] connection to pool created, socket ID 5
[23:12:40] (re?-)sending login request (for account #1: user WmtNwQw3Lsr34SxvgmpkmbgirMRxDKCAKVkB7X9YmMKm3P5pfLQRv5tMfEQtXk7MiHU4WyN3Eakg2Mvbe26eXSkP2H14HmQxd, pool mine.aeon-pool.com:8080) ...
[23:12:41] thread 15: share FOUND (context 1, nonce 0x000C3525)! (hash rate this thread = 109.96H/s)
[23:12:41] submitting share w/ difficulty 20000
[23:12:41] share ***accepted*** - yay!
[23:12:41] -> share accepted: 1/1 (100.00%) - total hashrate 3036.43H/s (may take a while to converge)
[23:12:47] thread 6: share FOUND (context 1, nonce 0x00463477)! (hash rate this thread = 134.895H/s)
[23:12:47] submitting share w/ difficulty 20000
[23:12:48] share ***accepted*** - yay!
[23:12:48] -> share accepted: 2/2 (100.00%) - total hashrate 4156.23H/s (may take a while to converge)
[23:13:01] thread 19: share FOUND (context 1, nonce 0x01036659)! (hash rate this thread = 124.643H/s)
[23:13:01] submitting share w/ difficulty 20000
[23:13:01] share ***accepted*** - yay!
[23:13:01] -> share accepted: 3/3 (100.00%) - total hashrate 4208.84H/s (may take a while to converge)
[23:13:03] thread 10: share FOUND (context 1, nonce 0x00DEC867)! (hash rate this thread = 141.022H/s)
[23:13:03] submitting share w/ difficulty 20000
[23:13:03] share ***accepted*** - yay!
[23:13:03] -> share accepted: 4/4 (100.00%) - total hashrate 4210.01H/s (may take a while to converge)
[23:13:03] new job at difficulty 30000.1
[23:13:06] thread 4: share FOUND (context 0, nonce 0x0033E30E)! (hash rate this thread = 141.62H/s)
[23:13:06] submitting share w/ difficulty 30000
[23:13:06] share ***accepted*** - yay!
[23:13:06] -> share accepted: 5/5 (100.00%) - total hashrate 4213.69H/s (may take a while to converge)
[23:13:16] thread 23: share FOUND (context 0, nonce 0x008C634C)! (hash rate this thread = 137.237H/s)
[23:13:16] submitting share w/ difficulty 30000
[23:13:16] share ***accepted*** - yay!
[23:13:16] -> share accepted: 6/6 (100.00%) - total hashrate 4217.06H/s (may take a while to converge)
[23:13:17] thread 16: share FOUND (context 0, nonce 0x0067C47E)! (hash rate this thread = 125.354H/s)
[23:13:17] submitting share w/ difficulty 30000
[23:13:17] share ***accepted*** - yay!
[23:13:17] -> share accepted: 7/7 (100.00%) - total hashrate 4216.50H/s (may take a while to converge)
[23:13:20] *** total hash rate: 4217H/s (may take a while to converge)
^X[23:13:22] thread 3: share FOUND (context 0, nonce 0x00AAEAA4)! (hash rate this thread = 131H/s)
[23:13:22] submitting share w/ difficulty 30000
[23:13:22] share ***accepted*** - yay!
[23:13:22] -> share accepted: 8/8 (100.00%) - total hashrate 4227.08H/s (may take a while to converge)
^C

Next i'll try it minig XMR.
 

bishop2020

New Member
Sep 1, 2013
7
2
3
I'm using the unified xmr-stak miner (CPU/GPU w/ XMR & Aeon support) on Win10:

i7-7820X - 2400H/s
980 TI (+250 OC) - 1200H/s

CPU-only my system power draw is ~200W, CPU+GPU is ~330W.
 

Janiashvili

Member
Dec 16, 2016
49
6
8
25
Is there a reason why evwryone uses xmrig? And is there a difference for thread optimization between xmr and aeon? (I.e. 2mb cache per thread?)
 

Klee

Well-Known Member
Jun 2, 2016
1,285
393
83
Is there a reason why evwryone uses xmrig? And is there a difference for thread optimization between xmr and aeon? (I.e. 2mb cache per thread?)
Easier to use in docker and easier to use with nvidia gpu's is the main reason, and it does really well mining Aeon.

I use xmrig-nvidia exclusively for my nvidia gpu's and I usually use xmrig with Ubuntu 17.10 (seems to be faster than xmr-stak-cpu on it), and older versions of xmr-stak-cpu, xmr-stak-cpu-dev.

Also I am playing around with Lukminer as it self configures way better than the newer versions of xmr-stak and is a little faster than xmrig.

It depends on what coin, what machine and sometimes ease of use at the time I run it as I experiment on a few other coins.

As of this moment with the coins i'm mining right now and that changes depending on the coin that I want to mine:

Dual E5-2620 v1 server runs xmrig-cpu 24/7 as it has almost four times the hashes mining Aeon (2000 H/s) compaired to Monero (525 H/s), also rarely Xmrig-nvidia running on the GTX 650 gpu to mine Monero or Aeon but that really hurts the desktop useability for not a lot of hash increase.

Open compute servers:
One E5-2660 node using the STH docker xmrig image.
One E5-2660 node running Lukminer.
Two E5-2660 nodes running Xmrig.
One E5-2665 node running Xmrig.
One E5-2665 node running Lukminer.

Test box running windows 7 with one Galaxy P106-104 running xmrig-nvidia.

Dual E5-2667 V3 es desktop running xmrig-nvidia on the GTX 1080 Ti when I am not on it.

The dual 2667 V3 pc is my main workstaion so I try out all the miners on the cpu's.

Xmr uses 2 mb per thread, Aeon only 1 mb per thread so you generally have 2-3 times the hash rate for Aeon.
 

Janiashvili

Member
Dec 16, 2016
49
6
8
25
I'm getting 2100-2200 (with many windows open, probably will be 100-200 hashes higher with nothing open) on dual E5-2640 v1 using XMR Stak, and yeah, it's way more taxing to the system than XMR, and I think stak's autoconfig did pretty good job - these CPUs have 15 MB of cache and autoconfig assigned them properly (3 threads using double the cache and rest using 1MB cache)


That means old 5600 series Xeons would be more efficient with Monero
 

Janiashvili

Member
Dec 16, 2016
49
6
8
25
@Janiashvili run one mining instance per CPU.
Thanks, it does slightly better, but second CPU is getting 1050 h/s while first is getting sub 1200 for some reason, and while both CPUs have 100% usage and same turbo speeds, first CPU has 66w usage while second has 62w; Could be some "features" of Windmill system
 

Janiashvili

Member
Dec 16, 2016
49
6
8
25
By the way checked and tried out and AEON calculations seem to be more precise than they are for other coins. Should have had miner around ~0.1 coin and actually have mined slightly more than .09 or more (some more may mature)
 

garetjax

Member
Nov 26, 2017
80
19
8
54
Just an update for your stats - my desktop intel processor i8600k at stock speed is now getting 1110.1 H/s running xmrig 2.4.3 on windows. I will be overclocking it to 5-5.1 ghz maybe this weekend which seems what most are getting with my particular motherboard.


upload_2017-12-6_22-8-17.png
 

Marsh

Moderator
May 12, 2013
2,274
1,085
113
You will need to join a Aeon mining pool to mine.
If you want to solo mining, you must run your own pool software, and you will need mega hashrate to find a bock.
 

alex_stief

Active Member
May 31, 2016
623
189
43
35
I am aware that income will be quite irregular without a larger pool. That is not my question. It comes down to: how to set up a private pool and which wallet to choose.

Edit: looking closely at the difficulty again, joining an existing pool seems like a good idea. I was just hesitant because while mining Monero in dwarfpool, about half of my block rewards went missing...
 
Last edited:

alex_stief

Active Member
May 31, 2016
623
189
43
35
I applied for STH pool.
Until then, I started mining in sumominer pool.
My dual AMD Epyc 7301 is pulling ~9500H/s @ 313W according to xmrig output. Although Sumominer is reporting a total of more than 10kH/s with spikes over 11kH/s... Edit: never mind, it already dropped to reasonable values
 
Last edited:

marcoi

Well-Known Member
Apr 6, 2013
1,391
220
63
Gotha Florida
I applied for STH pool.
Until then, I started mining in sumominer pool.
My dual AMD Epyc 7301 is pulling ~9500h/s @ 313W.
do you mind sharing rough build out of your server with prices? I'm trying to decide if i want to ramp up with old stock or get a new toy to play with as well while mining.
 

alex_stief

Active Member
May 31, 2016
623
189
43
35
You can find the build here: AMD Epyc build for fluid simulation (now with pics)
Prices...Apart from memory and SSDs for which I got lucky, all parts were purchased at regular prices (920€ für CPUs, 540€ for motherboard...). This was not a build for mining though, I don't think it can reach ROI any time soon.
Feel free to PM me or ask in the build thread if you need to know more, I think this is offtopic here.
 
Last edited: