I've compiled
my optimized code for each of the following architectures: core2, corei7, corei7-avx, core-avx-i, core-avx2, k8, k8-sse3, barcelona, bdver1, and bdver2
I've also compiled it via Visual Studio 2010 with performance guided optimizations for AMD, Intel, and blend processors (with and without AVX).
The end result is a
10 - 25% speed increase over the stock jh00 miner from yPool! (Even more if you're on Linux)
Donations appreciated! MTC: MEu8jBkkVvTLwvpiPjWC9YntyDH2u5KwVy
Which version is for me?For Linux users: compile the code from
githubgit clone https://github.com/llamasoft/xptminer-linux.git
cd xptminer-linux
CFLAGS="-flto -funroll-loops" make
Alternately, check out my
All-In-One EZ Setup Script.
For Windows users:For starters, you cannot go wrong with any of the "favor" versions.
They are compiled in a generic format that should work on
all processor architectures.
If you have an Intel processor, use "favorIntel".
If you have an AMD processor, try "favorBlend" then "favorAMD".
Architecture Specific Builds: (oldest to newest)
Intel
- core2
- corei7
- corei7-avx - a.k.a. "sandybridge"
- core-avx-i - a.k.a. "ivybridge"
- core-avx2 - a.k.a. "haswell / 4th generation i7"
AMD
- k8 - a.k.a. "opteron / athlon64"
- k8-sse3
- barcelona - a.k.a. "k10"
- bdver1 - a.k.a. "bulldozer"
- bdver2 - a.k.a. "piledriver"
Start with the oldest architecture of your processor manufacturer.
If the program works, write down the hash rate after 5-10 minutes* and try the next version.
If the program crashes, stop and use the previous version with the highest hash rate.
*: Seriously. At least 5 minutes. Before then and the hash rate is very inaccurate.Compare the results to the corresponding "favor" version.
Keep whichever is best!
Where do I get the binaries?The Windows 64-bit binaries are available for download from two locations:
https://mega.co.nz/#F!YsZSHYKA!IC8LK_MBGwqC-gWOpO7zoQhttps://www.dropbox.com/sh/wtxvxvkirxax2vj/9P_Rxb9V1y (dropbox mirror)
There is no 32-bit version of the optimized code for Windows.Part of the optimizations force the hash algorithms to use 64-bit mode. For more info,
see this post.
BenchmarksUser | CPU | Miner Version | kHash/s |
============ | ======================== | ============ | ============ |
gigawatt | AMD Phenom II x4 965 @ Stock | favorBlend | 637 |
gigawatt | Intel i5-3210M @ Stock | favorIntel | 292 |
gigawatt | Amazon AWS - c1.xlarge | github | 690 |
Want your benchmark added? Just post it in the thread and I'll update the list.