New M7i version of PTS miner is available and named yam - Yet Another Miner. Works with ypool.net and other pools that support XPT proto, including PTSPool.

yam M7i is complete rewrite of yvg1900 miner and has new cmd line and config options. Check readme.txt and yam.cfg for details.
It is faster on all supported platforms, including Win64, Linux64 and MacOS X 64.
PTS miner re-engineered for better support of different CPUs and now supports large pages on Windows. Check docs for more details.

yam M7i supports config files, backup pool connections, proxy and multiple connection handling improvements that reduce share rejections.
PTS miner now has better fine tuning, more precise stats and supports specifying per-thread memory size as configurable parameter.

yvg1900

P.S. M7h version will be available for Chinese users for some time at Baidu, but will be removed later on.

What I do not understand is if that thing with angel shares for >1000 PTS holders is terminated. If so, then why no announcement/explanation on that?

yvg1900

As it comes to software license, it is still not clear what positioning this group has to independent software developers that do not release source code due to various reasons.

yvg1900

What was the final AV after finetuning swithced to COMPLETED?

yvg1900

029xue,

Which kind of proxy support do you need? I am in progress on re-engineering miner connection layer for more reliable connections, so I may consider adding something.

Explain your usage scenario in more details.

yvg1900

After 512M typically memory bandwidth becomes bottleneck, but you shall try. Advise is very simple - try 512 and 1024, if 1024 is slower then 2048 will be even slower. If 1024 wins - try 2048. Stick with the fastest.

That's it.

yvg1900

Two processes make sense only for multi-socket systems (Duals, Quads, SGI UV, etc).

-A option added to lock threads to cores and minimize cross-core thread context migration. This helps in some cases and added to those who like to squeeze every single bit fo perf.

8 separate processes does not make sense at all. I am thinking on better internal NUMA support, too.

The main downside of running multiple processes is that every miner process shall maintain separate pool connection, while threads inside the process share one. Implementing proper NUMA support for single process is a non-trivial task, because of most important point is to get NUMA-aware memory allocation. This is on the list, but needs time for testing.

yvg1900