Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - yvg1900

Pages: 1 2 [3] 4 5 6 7 8 9 10 ... 14
31
BitShares PTS / Re: jhProtominer - CPU and collisions/min charts
« on: March 26, 2014, 09:46:38 pm »
Sooo, I finally got it solved.

Very silly mistake.

./yam --config yam-pts.cfg

you have to include the folder to yam-pts.cfg, for example:

./yam --config yam-yvg1900/linux64-core2/yam-pts.cfg

A "couldn't find the config file" mistake would be very nice for the next version. I hope I could help somebody out.
Anyway, thanks again for your efforts yvg1900, I'm nearly getting 100% improvement with this new version!  +5%

Will consider better error messages for M7o.

32
MemoryCoin / Re: New YAM version release
« on: March 24, 2014, 10:22:44 pm »
Support for AES-NI is essential for MMC mining - PoW is based on AES, so any hardware acceleration brings quite substantial benefits.

yam testing compatibility of optimization algos by performing reduced mining round on reference test data, and if some of required capabilities are not supported or not configured properly by BIOS and/or virtualization environment, it just crashes with Illegal Instruction or without message at all (this is configuration-dependent). Unfortunately, this is the only way to detect if some features really working or not. Relying on capabilities bits and CPU/OS feature detection is not reliable - there are many issues, including, for example, improper configuration of AVX2 on pre-SP1 Windows 7.

Additionally, from your logs, I see that you have not enough memory on your system to enable HugePages, and MemroyCoin PoW is extremely memory-intensive (as coin name suggests). This causes another level of underperformance, leading to very low hash rates.

33
mmc.gpools.com is not finding any blocks since very long time (actually, no single block found since I added support for it in yam). Contact form is also disabled.

I am considering to remove support for mmc.gpools.com from yam defaul config to avoid misleading.

Any objections? If none, I will remove it from M7o in favour of P2Pool.

34
MemoryCoin / Re: P2Pool Beta for Memorycoin
« on: March 22, 2014, 08:55:42 am »
Any news on yam compatibility version yet ?

still waiting for Stratum support.

Dont worry, I will be posting about it if I get any news :)

P2Pool and stratum support for PTS will come in M7o, and I am pushing it to be released this weekend. There are many small enhancements and improvements, so it is very time consuming, but I formally confirm that P2Pool is on the list for M7o.

35
MemoryCoin / Re: New YAM version release
« on: March 22, 2014, 08:28:54 am »
Only case I have similar behaviour (of gpu miner crashing time to time) is when I run heavily OCed AMD R9 290 with yam in parallel. You shall try to manually separate physical cores used by gpu miner and yam by setting cpu affinity. Ensure you are allocating complete core (not thread) for gpu miner.

Follow @yvg1900 on Twitter to get updates on performance mining software


36
MemoryCoin / Re: New YAM version release
« on: March 16, 2014, 06:28:37 pm »
Daniel,

You shall check if XEN kernel properly enables AES-NI instructions. Unfortunately, this is typical problem with virtualized environments, but you can start with generic build and switch off AES-NI by replacing aesni=on with aesni=off in mining params (consult readme.txt for more details).

If that works, try using another build while keeping aesni=off (you shall start with Sandy Bridge build, and fall back to Nehalem if that one fails). Then try making aesni=on, that brings major speedup but requires proper AES-NI support on the host.

Note that some CPU feqtures, incl. AES-NI, can be disabled in BIOS.

As of CPU scheduling, pinning and isolation, I am using either numactl (if available) or taskset. Another alternative will be to spin up additional lightweight guest and run yam from inside that guest.


Follow @yvg1900 on Twitter to get updates on performance mining software


37
This is a first. Finally some user friendly improvements to the pool.

 I would still like to use worker names with characters instead of numbers.

YAM won't accept my email address as the password.

According to URI encoding specs, some special characters shall be percent-encoded.

Look at https://app.zencoder.com/docs/guides/getting-started/special-characters-in-usernames-and-passwords for details and examples.

Check if that works for you, and report if not. I will take closer look on my side, too.

Follow @yvg1900 on Twitter to get updates on performance mining software


38
MemoryCoin / Re: Solo mining MMC using multiple yam workers
« on: March 08, 2014, 09:07:15 pm »
To be on the safe side with potential rejections, i recommend setting rpcthreads >= 2*number of workers. Actually yam uses very efficient conn implementation and takes maximum benefit of keep-alive http sessions, so reserving extra rpcthreads shall not create recognizable overhead.

Follow @yvg1900 on Twitter to get updates on performance mining software


39
MemoryCoin / Re: New YAM version release
« on: March 07, 2014, 07:17:35 pm »
Are there more optimization in the n version that was released quietly?
I just saw it was out.

MMC code contains minor changes in M7n, but has some reliability related changes in networking code, as well as support for more pools (incl. dwarfpool for mmc).

You can find change info @yvg1900 on Twitter.

40
MemoryCoin / Re: New YAM version release
« on: February 28, 2014, 06:28:04 pm »
Can you switch on timestamps and check time sync and timezone setup of your Mach?

Follow @yvg1900 on Twitter to get updates on performance mining software


41
MemoryCoin / Re: Yam-Miner on MacBook Pro (Mavericks)
« on: February 28, 2014, 07:11:09 am »
This is a known issue. Its original root is some incompatibility in C++ exception handling (GCC vs MacOS X shared libs). Practically this means that if you have any configuration error (i e yam can not find config file, some missing params, etc) you will get Trap 6. Simplest way to check is to COPY original yam-mmc.cfg file to yam executable directory and run

./yam -c yam-mmc.cfg

from terminal.

If that works, modify .cfg file with your parameters.

42
MemoryCoin / Re: New YAM version release
« on: February 28, 2014, 07:06:49 am »
As of AIX, can you provide more detailed specs of your mach?

43
MemoryCoin / Re: New YAM version release
« on: February 26, 2014, 12:53:57 pm »
Kernel in centos 5 is missing some very critical features and there is no plan to support it. This topic was under very detailed investigation, and final decision is no-go.

Follow @yvg1900 on Twitter to get updates on performance mining software


44
MemoryCoin / Re: New YAM version release
« on: February 26, 2014, 03:22:42 am »
CPU model shall be in form Intel Xeon E5-2697v2 or something like that. What tool displays this CPU model?

Follow @yvg1900 on Twitter to get updates on performance mining software


45
MemoryCoin / Re: New YAM version release
« on: February 25, 2014, 06:47:32 pm »
Thanks Yvg1900!

I'm a newbie, and just got a problem when I run with a Haswell-EP Xeon E-2600 CPU to mine the MMC, This is a Haswell CPU. But it seems the program always auto exit after below message:
-----------------------------------------------------------------
Checking MMC Stage 1 optimizations compatibility...
Checking MMC Stage 2 optimizations compatibility...
-----------------------------------------------------------------

I have tried each type folder, still the same issue.

but I can run the same program to mine the PTS on this CPU successfully. what's the problem? Is this CPU compatible with xpt protocol but getwork protocol?

very appreciate if you can answer my question.

Are you 100% sure you have Haswell-EP CPU? What is EXACT CPU model?

Pages: 1 2 [3] 4 5 6 7 8 9 10 ... 14