Nice to see some support for non AES CPUs
I'm currently using JCE on a Q6600 and I'm getting 66.79h/s
mcm gives me only 61.7h/s
Is there room for improvement here?
* ABOUT MCM/0.9.2 based on XMRig 2.8.1 gcc/5.4.0
* LIBS libuv/1.8.0 OpenSSL/1.0.2g microhttpd/0.9.44
* CPU Intel(R) Core(TM)2 Quad CPU @ 2.40GHz (1) x64 -AES
* CPU L2/L3 8.0 MB/0.0 MB
* THREADS 4, cryptonight, av=0, donate=1%
* ASSEMBLY auto:none
* POOL #1 pool.supportxmr.com:3333 variant auto
Topic: [CPU][XMR] Monero CPU Miner - page 2. (Read 1500 times)
0.9.2 Linux build added
New release for Monero fork
Releases: https://github.com/alex-tk/mcm/releases
v0.9.2
- added new algorithm CryptoNight variant 2 for Monero fork
- added CryptoNight-Lite and CryptoNight-Heavy support
- added SSL/TLS support for secure connections to pools
- based on xmrig 2.8.1
Releases: https://github.com/alex-tk/mcm/releases
v0.9.2
- added new algorithm CryptoNight variant 2 for Monero fork
- added CryptoNight-Lite and CryptoNight-Heavy support
- added SSL/TLS support for secure connections to pools
- based on xmrig 2.8.1
You can check threads count at startup, it will display: "* THREADS: [number]"
I know. It's 4 now.
The pool and the miner calculate hashrate in different ways. The pool calculates it based on found shares. The miner calculates it based on generated hashes.What hashrate is in the miner?
85.7 H/s avg: 86.4 H/s max: 93.6 H/s
The hashrate shown by pool should be based on what they receive from my miner in a period of time.
I rely on what the pool tells because long ago the Monero miners used to show nice hashrates, but they've got disconnected very often leading to a lot of lost work and much lower paid hashrate.
However, I think that I will stop the miner, since it would need half a year to get to minimum payout
The command line didn't work, it didn't care of my setting. I've set to 4 in the config.
The hashrate displayed by the pool has big variations, between 33 and 200 H/s, having the 6h average 90 H/s and 3h average 77 H/s. So the setting change doesn't seem to help.
The hashrate displayed by the pool has big variations, between 33 and 200 H/s, having the 6h average 90 H/s and 3h average 77 H/s. So the setting change doesn't seem to help.
You can check threads count at startup, it will display: "* THREADS: [number]"
The pool and the miner calculate hashrate in different ways. The pool calculates it based on found shares. The miner calculates it based on generated hashes.What hashrate is in the miner?
It seems that auto detection failed and set treads count to 5 (that's why cpu usage 66% - 5/8), but for your cpu it would be better 4, try to set it manualty "-t 4" for command line or "threads: 5" in config file, it should increase hashrate
The command line didn't work, it didn't care of my setting. I've set to 4 in the config.
The hashrate displayed by the pool has big variations, between 33 and 200 H/s, having the 6h average 90 H/s and 3h average 77 H/s. So the setting change doesn't seem to help.
I've done today a test, since I have at hand an older computer where it doesn't matter if the miner is safe or not.
CPU is i7-920, CPU L2/L3 1/8
The hashrate reported by the pool is 87 H/s = the average for the last 3 hours.
If I remember right, the old miners (way more than one year ago) were showing 75-80 H/s, and they were using the CPU 100%, while this one uses 66%.
So the numbers look pretty good. All this is on default command line and config, do I have to change anything?
CPU is i7-920, CPU L2/L3 1/8
The hashrate reported by the pool is 87 H/s = the average for the last 3 hours.
If I remember right, the old miners (way more than one year ago) were showing 75-80 H/s, and they were using the CPU 100%, while this one uses 66%.
So the numbers look pretty good. All this is on default command line and config, do I have to change anything?
It seems that auto detection failed and set treads count to 5 (that's why cpu usage 66% - 5/8), but for your cpu it would be better 4, try to set it manualty "-t 4" for command line or "threads: 5" in config file, it should increase hashrate
Please post you hashrates.
I've done today a test, since I have at hand an older computer where it doesn't matter if the miner is safe or not.
CPU is i7-920, CPU L2/L3 1/8
The hashrate reported by the pool is 87 H/s = the average for the last 3 hours.
If I remember right, the old miners (way more than one year ago) were showing 75-80 H/s, and they were using the CPU 100%, while this one uses 66%.
So the numbers look pretty good. All this is on default command line and config, do I have to change anything?
new release v0.9.1: 2% performance boost for --av=0 (Software AES implementation)
I want to use a processor for mining XMR which processor is more efficient? Advise please.
If you plan to upgrade your pc new cpu on which you want get some xmr then AMD Ryzen is great choice - they have a lot of L3 cache. So even Ryzen 3 1200 will perform about 250H/s. To get more details you can use http://monerobenchmarks.info/singleCPUAMDINTEL.php. The main rule - 1.5-2M of cache per thread.
From the info in GitHub the dev fee is 1%.
I would love some feedback - if it's indeed faster than others and if it doesn't contain other.. surprises (no offense, dev, but being a little suspicious never hurts)
I would love some feedback - if it's indeed faster than others and if it doesn't contain other.. surprises (no offense, dev, but being a little suspicious never hurts)
Yes it is big problem that antiviruses detect it as dangerous software (Rule: XMRIG_Monero_Miner Ruleset: CryptoCoin Miner). People afraid to use such software. So I have to rewrite all from scratch. It will take some time.
Most crypto miners are detected by antiviruses. That's why I didn't even bother to check with VirusTotal.
But a miner you actually allow to run on your computer can do many more, even searching the HDD for wallets or downloading a payload that does that. I mean, it's just some code and the possibilities are limitless.
That's why I'll wait for trusted 3rd party to review the code.
From the info in GitHub the dev fee is 1%.
I would love some feedback - if it's indeed faster than others and if it doesn't contain other.. surprises (no offense, dev, but being a little suspicious never hurts)
I would love some feedback - if it's indeed faster than others and if it doesn't contain other.. surprises (no offense, dev, but being a little suspicious never hurts)
Yes it is big problem that antiviruses detect it as dangerous software (Rule: XMRIG_Monero_Miner Ruleset: CryptoCoin Miner). People afraid to use such software. So I have to rewrite all from scratch. It will take some time.
I want to use a processor for mining XMR which processor is more efficient? Advise please.
How much is the devfee?
SSE4, so this can potentially make (E7+) Core2Duo's hashrate competent enough to earn a profit?
I'd love to try this with my scrap machines.
Waiting for a legit test response or a code review.
SSE4, so this can potentially make (E7+) Core2Duo's hashrate competent enough to earn a profit?
I'd love to try this with my scrap machines.
Waiting for a legit test response or a code review.
E7+ with 3M of L2 can be run in 2 threads and with expected hashrate about 60H/s. The biggest boost will be for older architectures like Yorkfield/Wolfdale about 40-50%, for newer it will be less (ex Haswell about 15-20%). For AES-NI it is about 1% for now.
How much is the devfee?
SSE4, so this can potentially make (E7+) Core2Duo's hashrate competent enough to earn a profit?
I love to try this with my scrap machines.
SSE4, so this can potentially make (E7+) Core2Duo's hashrate competent enough to earn a profit?
I love to try this with my scrap machines.
From the info in GitHub the dev fee is 1%.
I would love some feedback - if it's indeed faster than others and if it doesn't contain other.. surprises (no offense, dev, but being a little suspicious never hurts)
How much is the devfee?
SSE4, so this can potentially make (E7+) Core2Duo's hashrate competent enough to earn a profit?
I'd love to try this with my scrap machines.
Waiting for a legit test response or a code review.
SSE4, so this can potentially make (E7+) Core2Duo's hashrate competent enough to earn a profit?
I'd love to try this with my scrap machines.
Waiting for a legit test response or a code review.
Linux build added
MCM is Monero (XMR) CPU miner with the best performance. Originally based on xmrig (net and config) with completely rewritten algo from scratch on ASM.
On SSE4 (non AES-NI) cpu performance boost is up to 50% (depends on cpu architecture). More description on Github: https://github.com/alex-tk/mcm
Releases: https://github.com/alex-tk/mcm/releases
v0.9.6
- added support for new algorithm cryptonight/r, short alias cn/r (also known as CryptoNightR or CryptoNight variant 4), for upcoming Monero fork
v0.9.5
- added new algorithm cn-pico/trtl (aliases cryptonight-turtle, cn-trtl) for TurtleCoin (TRTL) fork.
- added new algorithm cn/half for Masari and Stellite forks.
v0.9.4
+20% for cn/2 (CryptoNight variant 2 for Monero fork) --av=3 (Software AES implementation).
v0.9.3
- performance boost for CryptoNight variant 2 for Monero fork --av=3 (Software AES implementation)
v0.9.2
- added new algorithm CryptoNight variant 2 for Monero fork
- added CryptoNight-Lite and CryptoNight-Heavy support
- added SSL/TLS support for secure connections to pools
- based on xmrig 2.8.1 (https://github.com/xmrig/xmrig/blob/master/README.md)
v0.9.1
+2% performance boost for --av=0 (Software AES implementation)
Core2 Quad Q9300 2.5 GHz 6M, 1 & 4 threads, 64-bits, Software AES implementation
Please post you hashrates.
On SSE4 (non AES-NI) cpu performance boost is up to 50% (depends on cpu architecture). More description on Github: https://github.com/alex-tk/mcm
Releases: https://github.com/alex-tk/mcm/releases
v0.9.6
- added support for new algorithm cryptonight/r, short alias cn/r (also known as CryptoNightR or CryptoNight variant 4), for upcoming Monero fork
v0.9.5
- added new algorithm cn-pico/trtl (aliases cryptonight-turtle, cn-trtl) for TurtleCoin (TRTL) fork.
- added new algorithm cn/half for Masari and Stellite forks.
v0.9.4
+20% for cn/2 (CryptoNight variant 2 for Monero fork) --av=3 (Software AES implementation).
v0.9.3
- performance boost for CryptoNight variant 2 for Monero fork --av=3 (Software AES implementation)
v0.9.2
- added new algorithm CryptoNight variant 2 for Monero fork
- added CryptoNight-Lite and CryptoNight-Heavy support
- added SSL/TLS support for secure connections to pools
- based on xmrig 2.8.1 (https://github.com/xmrig/xmrig/blob/master/README.md)
v0.9.1
+2% performance boost for --av=0 (Software AES implementation)
Core2 Quad Q9300 2.5 GHz 6M, 1 & 4 threads, 64-bits, Software AES implementation
| algo | cn/r | cn/2 | cn-lite/1 | cn-trtl |
| mcm 0.9.6 | 60 | 84 | 234 | 760 |
| xmrig 2.13.1 | 54 | 50 | 158 | 760 |
Please post you hashrates.
Jump to: