Author Topic: [ANN] MMCPool.com - GPU,CPU(yam) - The Awesomest Pool!  (Read 125752 times)

0 Members and 1 Guest are viewing this topic.

Offline reorder

  • Sr. Member
  • ****
  • Posts: 400
    • View Profile
M7j version of yam miner available. It supports fast CPU mining for PTS, MMC, more mining pools and protocols.

To mine MemoryCoin with yam M7j use provided miner config template named yam-mmc.cfg as a base, check readme.txt for more details.
yam M7j optimised for mining MMC on CPUs with AES-NI support and has 5 different algo variations for HT, non-HT and GPU friendly setups.

yam M7j miner now supports PTS mining at beeeeer and includes fix for Win2003 and other older 64bit systems. Check readme.txt for details.

Download at:
https://www.dropbox.com/sh/jvp4wwek8jpohj7/RlW6hzYqTz
https://mega.co.nz/#F!h0tkXSxZ!f62uoUXogkxQmP2xO8Ib-g
http://sdrv.ms/18wfjYX
http://pan.baidu.com/s/1xOOWa

yvg1900

It seems that they are compile at linux-core 2.6.24. But almost all my servers are runing at lower kernel such as 2.6.18. Could you please just recompile with older kernel or can you share source code to me? I can compile in my environment. Thank you so much...
If 2.6.18 means CenOS 5, then AES-NI is not available there. You have to write (or find) a driver that would enable it.

Offline leechs

  • Newbie
  • *
  • Posts: 7
    • View Profile
M7j version of yam miner available. It supports fast CPU mining for PTS, MMC, more mining pools and protocols.

To mine MemoryCoin with yam M7j use provided miner config template named yam-mmc.cfg as a base, check readme.txt for more details.
yam M7j optimised for mining MMC on CPUs with AES-NI support and has 5 different algo variations for HT, non-HT and GPU friendly setups.

yam M7j miner now supports PTS mining at beeeeer and includes fix for Win2003 and other older 64bit systems. Check readme.txt for details.

Download at:
https://www.dropbox.com/sh/jvp4wwek8jpohj7/RlW6hzYqTz
https://mega.co.nz/#F!h0tkXSxZ!f62uoUXogkxQmP2xO8Ib-g
http://sdrv.ms/18wfjYX
http://pan.baidu.com/s/1xOOWa

yvg1900

It seems that they are compile at linux-core 2.6.24. But almost all my servers are runing at lower kernel such as 2.6.18. Could you please just recompile with older kernel or can you share source code to me? I can compile in my environment. Thank you so much...

Offline jorneyflair

  • Jr. Member
  • **
  • Posts: 21
    • View Profile
With the new coin miner fully justifies its name.  :)

Yes! Thanks for bringing mining home to CPUs and Memory. 5000 MMC tip on its way to yvg1900 from MCF.

yvg1900 should be the CTO i think

Only if he open-sources his code!  As CTO he would be getting paid anyway.

agreed, he needs to open it if wanna get the position.

Offline sth

  • Newbie
  • *
  • Posts: 7
    • View Profile
I'm mining with a couple of CPU's and I've gone from about 30 coins/day to 4 coins/day in a few days. A big rise in difficulty or is it the new GPU miners that's taking over?
PTS: PaLMohgzkpot2biUPsTEkfW1geMfrSYVjw
BTC: 19ifwoJs1DoFVSoPtNfS8EKhAsxBQGuVsD

Offline frostybutdelicious

  • Newbie
  • *
  • Posts: 2
    • View Profile
I'm on windows, and when I enter this command downloads\yam....\yam....\yam.exe --config yam-mmc.cfg it tells me I need to specify at least one --mine parameter. But those are specified in the config file, so I'm not sure how to proceed. Any ideas?
« Last Edit: January 16, 2014, 06:46:05 am by frostybutdelicious »

Offline skaffen

  • Jr. Member
  • **
  • Posts: 25
    • View Profile
With the new coin miner fully justifies its name.  :)

Yes! Thanks for bringing mining home to CPUs and Memory. 5000 MMC tip on its way to yvg1900 from MCF.

yvg1900 should be the CTO i think

Only if he open-sources his code!  As CTO he would be getting paid anyway.
MMC: MLh27rbqmDWr6w9V5rWDV6pUFjganJhZv3
PTS:  Pf53gFMhCToW2nGovRKfRc4tWoXBY1A3Pq

Offline jorneyflair

  • Jr. Member
  • **
  • Posts: 21
    • View Profile
With the new coin miner fully justifies its name.  :)

Yes! Thanks for bringing mining home to CPUs and Memory. 5000 MMC tip on its way to yvg1900 from MCF.

yvg1900 should be the CTO i think

Offline glitchboy

  • Full Member
  • ***
  • Posts: 55
    • View Profile
    • MMCPool.com
MMCPool.com - MemoryCoin 2.0 Pool

Offline Edvin512

  • Newbie
  • *
  • Posts: 1
    • View Profile
Target OK
Error: boost::bad_any_cast: failed conversion using boost::any_cast

Any idea what can be wrong?

Offline sandor111

  • Newbie
  • *
  • Posts: 10
    • View Profile
Yeah I'm pretty bummed out, but 3 extra hpm is compared to previous miners is cool.

Offline badbonez

  • Full Member
  • ***
  • Posts: 50
    • View Profile
With a dual L5639 I get 13 hpm on 24 threads, not a huge improvement over the previous miners, definitely not 300% (btw I'm using Nehalem binary)

I'm just trying to get the miner to run on all 24 threads.  When I try just 12 threads, I get about 11HPM, I was hoping (maybe too optimistic) that 24 threads = ~22HPM.  But I'm paying for the 24 threads on the cloud server, I want to use them all.
MMC: MQ4EA85nnZwytrcqx9rJSpDWVTSXaxfqmc

Offline sandor111

  • Newbie
  • *
  • Posts: 10
    • View Profile
With a dual L5639 I get 13 hpm on 24 threads, not a huge improvement over the previous miners, definitely not 300% (btw I'm using Nehalem binary)
« Last Edit: January 14, 2014, 07:49:29 pm by sandor111 »

Offline badbonez

  • Full Member
  • ***
  • Posts: 50
    • View Profile
I appreciate the help!  I am using a 6-core (L5639), 24 thread Unbutu 13.04 server.  When I run ./yam -c yam-mmc.cfg it runs for about 20-30 seconds and then dies.  If I run yam with say 12 threads, it works fine.  But I'd rather not run multiple instances. (NOTE:  It will not work if I run 2x 12 thread instances. If I run a 12 th and a 8 th instance I get a combined HPM of ~12.  About the same if I just ran a single 12 thread instance.)

I have added my configuration file, cpuinfo, meminfo and output of the miner below.

Here is my config file:

Code: [Select]
threads = 0
mining-params = mmc:av=1&aesni=on
mine = getwork://MLzSj31GVDqYLstZjFFqoGjafhiGz5FkRo@work.mmcpool.com:80:8880:8881:8882:8883/mmc
mine = getwork://MLzSj31GVDqYLstZjFFqoGjafhiGz5FkRoGe@mmcpool.1gh.com:8080:8081:8082:8083/mmc
#proxy = socks4a://127.0.0.1:9150
compact-stats = 1
print-timestamps = 1

CPUINFO:

Code: [Select]
processor : 23
vendor_id : GenuineIntel
cpu family : 6
model : 44
model name : Intel(R) Xeon(R) CPU           L5639  @ 2.13GHz
stepping : 2
microcode : 0x15
cpu MHz : 1600.000
cache size : 12288 KB
physical id : 1
siblings : 12
core id : 10
cpu cores : 6
apicid : 53
initial apicid : 53
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 popcnt aes lahf_lm ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid
bogomips : 4266.84
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:

MEMINFO:

Code: [Select]
MemTotal:       24682120 kB
MemFree:        24314448 kB
Buffers:             812 kB
Cached:             5656 kB
SwapCached:         3136 kB
Active:             3996 kB
Inactive:          11040 kB
Active(anon):       3344 kB
Inactive(anon):     5288 kB
Active(file):        652 kB
Inactive(file):     5752 kB
Unevictable:           0 kB
Mlocked:               0 kB
SwapTotal:         93180 kB
SwapFree:          75052 kB
Dirty:                 0 kB
Writeback:             0 kB
AnonPages:          5644 kB
Mapped:             1236 kB
Shmem:                12 kB
Slab:              69792 kB
SReclaimable:      27676 kB
SUnreclaim:        42116 kB
KernelStack:        1680 kB
PageTables:         1860 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:    12434240 kB
Committed_AS:      63616 kB
VmallocTotal:   34359738367 kB
VmallocUsed:      332044 kB
VmallocChunk:   34346626364 kB
HardwareCorrupted:     0 kB
AnonHugePages:         0 kB
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
DirectMap4k:       48320 kB
DirectMap2M:     4136960 kB
DirectMap1G:    20971520 kB

Here's the output of the miner:

Code: [Select]
Loading config file [yam-mmc.cfg]
[2014-01-14 09:41:56.838847] Miner version: yam M7j-linux64-generic/yvg1900
[2014-01-14 09:41:56.839029] Checking target [getwork://MLzSj31GVDqYLstZjFFqoGjafhiGz5FkRo@work.mmcpool.com:80:8880:8881:8882:8883/mmc]...
[2014-01-14 09:41:56.840281] Target OK
[2014-01-14 09:41:56.840359] Checking target [getwork://MLzSj31GVDqYLstZjFFqoGjafhiGz5FkRoGe@mmcpool.1gh.com:8080:8081:8082:8083/mmc]...
[2014-01-14 09:41:56.840425] Target OK
[2014-01-14 09:41:56.840490] Checking target [getwork://badbonez.mac:xxxx@mmc.gpools.com:8080/mmc]...
[2014-01-14 09:41:56.840551] Target OK
[2014-01-14 09:41:56.840578] Checking params [mmc:av=1&aesni=on]...
[2014-01-14 09:41:56.840620] Params OK
[2014-01-14 09:41:56.841237] Checking MMC Stage 1 optimizations compatibility...
[2014-01-14 09:41:56.841342] Checking MMC Stage 2 optimizations compatibility...
[2014-01-14 09:41:56.842703] OK: MMC optimizations are compatible
[2014-01-14 09:41:56.842931] MemoryCoin: Memory usage 1024M per thread, Algorithm Variation 1
[2014-01-14 09:41:56.843012] Using 24 mining threads
[2014-01-14 09:41:56.845115]   Will mine 24 rounds for miner developers to support development of the next version
[2014-01-14 09:41:56.845344]   Follow @yvg1900 on Twitter to get information on new version availability on time
[2014-01-14 09:41:57.362127] New MemoryCoin Block nTime 1389721330
[2014-01-14 09:41:57.860896] MMC Agg. SPM: ?, HPM: ?; Rnds C/I: 0/0, Don. C/I: 0/0; Cfg/Thr SPM: ?/?, Cfg/Thr HPM: ?/? 0 rnds AV=1, ART=?
[2014-01-14 09:41:57.860948]   work.mmcpool.com: On-line, Shares Submitted 0, Accepted 0
[2014-01-14 09:41:57.860977]   mmcpool.1gh.com: Idle, Shares Submitted 0, Accepted 0
[2014-01-14 09:41:57.860997]   mmc.gpools.com: Idle, Shares Submitted 0, Accepted 0
[2014-01-14 09:42:02.139607] New MemoryCoin Block nTime 1389721335
[2014-01-14 09:42:07.860886] MMC Agg. SPM: ?, HPM: ?; Rnds C/I: 0/0, Don. C/I: 0/0; Cfg/Thr SPM: ?/?, Cfg/Thr HPM: ?/? 0 rnds AV=1, ART=?
[2014-01-14 09:42:07.860940]   work.mmcpool.com: On-line, Shares Submitted 0, Accepted 0
[2014-01-14 09:42:07.860966]   mmcpool.1gh.com: Idle, Shares Submitted 0, Accepted 0
[2014-01-14 09:42:07.860985]   mmc.gpools.com: Idle, Shares Submitted 0, Accepted 0
[2014-01-14 09:42:08.504830] New MemoryCoin Block nTime 1389721340
[2014-01-14 09:42:12.270875] New MemoryCoin Block nTime 1389721344
[2014-01-14 09:42:17.860886] MMC Agg. SPM: ?, HPM: ?; Rnds C/I: 0/0, Don. C/I: 0/0; Cfg/Thr SPM: ?/?, Cfg/Thr HPM: ?/? 0 rnds AV=1, ART=?
[2014-01-14 09:42:17.860940]   work.mmcpool.com: On-line, Shares Submitted 0, Accepted 0
[2014-01-14 09:42:17.860964]   mmcpool.1gh.com: Idle, Shares Submitted 0, Accepted 0
[2014-01-14 09:42:17.860982]   mmc.gpools.com: Idle, Shares Submitted 0, Accepted 0
Killed


Thank you!




Unfortunately, here we have nearly the same situation as we had with cloud servers running first versions of PTS mining (before yam, it was jhProtominer M7c-M7h, probably you followed a bit).

I recommend you the following:

1. Post here output of the miner that comes right after banner message - there is info on algo in use, number of threads selected and optimization compatibility checks - there we will see if AES-NI is really working
2. Try running it with ONE thread. You shall get ART value within reasonable time and factor out many potential issues.
3. Post here output of numactl --hardware (this is TYPICAL that cloud services DO NOT properly support NUMA, to be honest I am NOT aware of any that does that right, as well as memory management is completely unacceptable for high performance computing).

From what I see, you have multi-socket system (some Dual Xeon E5-26XX), so proper NUMA support is critical. Default memory allocation policy for such systems is typical to be Interleaved, causing huge underperformance under heavy memory load due to QPI bandwidth limitation, which is exactly our case.

Note that miner updates statistics in between rounds, so not showing statistics means that round takes way too long - compare this with physical machine - some SB, IB or Haswell i7.

As of crash, which EXACTLY CPU is there and which build do you use?

yvg1900

P.S. In other case I would not support cloud services and low end configs because of they simply using outdated and improperly configured software. But let us try to figure out what we can do.
« Last Edit: January 14, 2014, 06:22:50 pm by badbonez »
MMC: MQ4EA85nnZwytrcqx9rJSpDWVTSXaxfqmc

Offline Armchair Miner

  • Newbie
  • *
  • Posts: 8
    • View Profile
Great job    yvg1900!! Trippling the performance both on i7 3770k with the ivy bridge build and on AMD FX 8350 with the generic build.

Being that the CPUs are about $200 and GPUs about $400, CPU's are now operating at parity with the GPUs in  $/Hash !

Frostybutdelicious, the "generic" build works well for the AMD FX. Using 6 threads the performance is almost at parity with the i7 3770k.

Wearing some bling \    /  and -($)-($)- today.
                                   $

M7j version of yam miner available. It supports fast CPU mining for PTS, MMC, more mining pools and protocols.

To mine MemoryCoin with yam M7j use provided miner config template named yam-mmc.cfg as a base, check readme.txt for more details.
yam M7j optimised for mining MMC on CPUs with AES-NI support and has 5 different algo variations for HT, non-HT and GPU friendly setups.

yam M7j miner now supports PTS mining at beeeeer and includes fix for Win2003 and other older 64bit systems. Check readme.txt for details.

Download at:
https://www.dropbox.com/sh/jvp4wwek8jpohj7/RlW6hzYqTz
https://mega.co.nz/#F!h0tkXSxZ!f62uoUXogkxQmP2xO8Ib-g
http://sdrv.ms/18wfjYX
http://pan.baidu.com/s/1xOOWa

yvg1900

I've got 2 computers running windows 7. One is an 8 core AMD FX cpu and the other is a 4 core AMD FX cpu. Which version of the miner am I supposed to used? Also, is it possible to solo mine protoshares or memorycoin using this miner, or is it only possible to use a pool?

EDIT: my i7 3770k works with ivy bridge not sandy bridge.
« Last Edit: January 15, 2014, 02:14:27 am by Armchair Miner »

Offline OpenCLGuy

  • Newbie
  • *
  • Posts: 2
    • View Profile
Code: [Select]
13:51:31.013 [GPU0] Platform: Intel(R) OpenCL
13:51:31.013 [GPU0] Device: Intel(R) HD Graphics 4000
13:51:31.013 [GPU0] Total device memory: 1624 MB
13:51:31.013 [GPU0] Maximum buffer size: 406 MB
13:51:31.013 [GPU0] Cannot use the device! Maximum buffer size is less than 1024
MB
13:51:31.013 [GPU1] Platform: NVIDIA CUDA
13:51:31.013 [GPU1] Device: GeForce 610M
13:51:31.013 [GPU1] Total device memory: 2048 MB
13:51:31.013 [GPU1] Maximum buffer size: 512 MB
13:51:31.013 [GPU1] Cannot use the device! Maximum buffer size is less than 1024
MB
13:51:31.013 [GPU2] Device not found
13:51:31.013 Started 0 miner threads

nooo    :'(

is possible set the program for use in Maximum buffer size 512?

I've just updated the miner. It now tries to allocate 1GB buffer regardless of what the driver reports. You could try if it works on your card. Anyway the 610's performance will be disappointing. You'll get much more with any modern CPU and yam miner.