SHARE
TWEET

Xmr-config

a guest Jun 8th, 2017 7,424 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. /*
  2.  * Thread configuration for each thread. Make sure it matches the number above.
  3.  * low_power_mode - This mode will double the cache usage, and double the single thread performance. It will  
  4.  *                  consume much less power (as less cores are working), but will max out at around 80-85% of  
  5.  *                  the maximum performance.
  6.  *
  7.  * no_prefetch -    Some sytems can gain up to extra 5% here, but sometimes it will have no difference or make
  8.  *                  things slower.
  9.  *
  10.  * affine_to_cpu -  This can be either false (no affinity), or the CPU core number. Note that on hyperthreading  
  11.  *                  systems it is better to assign threads to physical cores. On Windows this usually means selecting  
  12.  *                  even or odd numbered cpu numbers. For Linux it will be usually the lower CPU numbers, so for a 4  
  13.  *                  physical core CPU you should select cpu numbers 0-3.
  14.  *
  15.  * On the first run the miner will look at your system and suggest a basic configuration that will work,
  16.  * you can try to tweak it from there to get the best performance.
  17.  *  
  18.  * A filled out configuration should look like this:
  19.  * "cpu_threads_conf" :
  20.  * [  
  21.  *      { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 0 },
  22.  *      { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 1 },
  23.  * ],
  24.  */
  25. "cpu_threads_conf" :  
  26. [  
  27.          { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 0 },
  28.     { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 2 },
  29.     { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 4 },
  30.     { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 6 },
  31.     { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 1 },
  32.     { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 3 },
  33.     { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 5 },
  34.  ],
  35.  
  36. /*
  37.  * LARGE PAGE SUPPORT
  38.  * Lare pages need a properly set up OS. It can be difficult if you are not used to systems administation,
  39.  * but the performace results are worth the trouble - you will get around 20% boost. Slow memory mode is
  40.  * meant as a backup, you won't get stellar results there. If you are running into trouble, especially
  41.  * on Windows, please read the common issues in the README.
  42.  *
  43.  * By default we will try to allocate large pages. This means you need to "Run As Administrator" on Windows.
  44.  * You need to edit your system's group policies to enable locking large pages. Here are the steps from MSDN
  45.  *
  46.  * 1. On the Start menu, click Run. In the Open box, type gpedit.msc.
  47.  * 2. On the Local Group Policy Editor console, expand Computer Configuration, and then expand Windows Settings.
  48.  * 3. Expand Security Settings, and then expand Local Policies.
  49.  * 4. Select the User Rights Assignment folder.
  50.  * 5. The policies will be displayed in the details pane.
  51.  * 6. In the pane, double-click Lock pages in memory.
  52.  * 7. In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.
  53.  * 8. In the Select Users, Service Accounts, or Groups dialog box, add an account that you will run the miner on
  54.  * 9. Reboot for change to take effect.
  55.  *
  56.  * Windows also tends to fragment memory a lot. If you are running on a system with 4-8GB of RAM you might need
  57.  * to switch off all the auto-start applications and reboot to have a large enough chunk of contiguous memory.
  58.  *
  59.  * On Linux you will need to configure large page support "sudo sysctl -w vm.nr_hugepages=128" and increase your
  60.  * ulimit -l. To do do this you need to add following lines to /etc/security/limits.conf - "* soft memlock 262144"
  61.  * and "* hard memlock 262144". You can also do it Windows-style and simply run-as-root, but this is NOT
  62.  * recommended for security reasons.
  63.  *
  64.  * Memory locking means that the kernel can't swap out the page to disk - something that is unlikey to happen on a  
  65.  * command line system that isn't starved of memory. I haven't observed any difference on a CLI Linux system between  
  66.  * locked and unlocked memory. If that is your setup see option "no_mlck".  
  67.  */
  68.  
  69. /*
  70.  * use_slow_memory defines our behaviour with regards to large pages. There are three possible options here:
  71.  * always  - Don't even try to use large pages. Always use slow memory.
  72.  * warn    - We will try to use large pages, but fall back to slow memory if that fails.
  73.  * no_mlck - This option is only relevant on Linux, where we can use large pages without locking memory.
  74.  *           It will never use slow memory, but it won't attempt to mlock
  75.  * never   - If we fail to allocate large pages we will print an error and exit.
  76.  */
  77. "use_slow_memory" : "never",
  78.  
  79. /*
  80.  * NiceHash mode
  81.  * nicehash_nonce - Limit the noce to 3 bytes as required by nicehash. This cuts all the safety margins, and
  82.  *                  if a block isn't found within 30 minutes then you might run into nonce collisions. Number
  83.  *                  of threads in this mode is hard-limited to 32.
  84.  */
  85. "nicehash_nonce" : false,
  86.  
  87. /*
  88.  * TLS Settings
  89.  * If you need real security, make sure tls_secure_algo is enabled (otherwise MITM attack can downgrade encryption
  90.  * to trivially breakable stuff like DES and MD5), and verify the server's fingerprint through a trusted channel.  
  91.  *
  92.  * use_tls         - This option will make us connect using Transport Layer Security.
  93.  * tls_secure_algo - Use only secure algorithms. This will make us quit with an error if we can't negotiate a secure algo.
  94.  * tls_fingerprint - Server's SHA256 fingerprint. If this string is non-empty then we will check the server's cert against it.
  95.  */
  96. "use_tls" : false,
  97. "tls_secure_algo" : true,
  98. "tls_fingerprint" : "",
  99.  
  100. /*
  101.  * pool_address      - Pool address should be in the form "pool.supportxmr.com:3333". Only stratum pools are supported.
  102.  * wallet_address - Your wallet, or pool login.
  103.  * pool_password  - Can be empty in most cases or "x".
  104.  */
  105. "pool_address" : "pool.minexmr.com:4444",
  106. "wallet_address" : "41hFK3vXafy6WvuDqWZ9nZD1kMuaos54FZnjodhmJ2iL19VvHA2xcN4XWgqyiCcEZGUXFnjektRqA9UqvUSRYv5S3m7PWgr.rig01",
  107. "pool_password" : "x",
  108.  
  109. /*
  110.  * Network timeouts.
  111.  * Because of the way this client is written it doesn't need to constantly talk (keep-alive) to the server to make  
  112.  * sure it is there. We detect a buggy / overloaded server by the call timeout. The default values will be ok for  
  113.  * nearly all cases. If they aren't the pool has most likely overload issues. Low call timeout values are preferable -
  114.  * long timeouts mean that we waste hashes on potentially stale jobs. Connection report will tell you how long the
  115.  * server usually takes to process our calls.
  116.  *
  117.  * call_timeout - How long should we wait for a response from the server before we assume it is dead and drop the connection.
  118.  * retry_time    - How long should we wait before another connection attempt.
  119.  *                Both values are in seconds.
  120.  * giveup_limit - Limit how many times we try to reconnect to the pool. Zero means no limit. Note that stak miners
  121.  *                don't mine while the connection is lost, so your computer's power usage goes down to idle.
  122.  */
  123. "call_timeout" : 10,
  124. "retry_time" : 10,
  125. "giveup_limit" : 0,
  126.  
  127. /*
  128.  * Output control.
  129.  * Since most people are used to miners printing all the time, that's what we do by default too. This is suboptimal
  130.  * really, since you cannot see errors under pages and pages of text and performance stats. Given that we have internal
  131.  * performance monitors, there is very little reason to spew out pages of text instead of concise reports.
  132.  * Press 'h' (hashrate), 'r' (results) or 'c' (connection) to print reports.
  133.  *
  134.  * verbose_level - 0 - Don't print anything.  
  135.  *                 1 - Print intro, connection event, disconnect event
  136.  *                 2 - All of level 1, and new job (block) event if the difficulty is different from the last job
  137.  *                 3 - All of level 1, and new job (block) event in all cases, result submission event.
  138.  *                 4 - All of level 3, and automatic hashrate report printing  
  139.  */
  140. "verbose_level" : 4,
  141.  
  142. /*
  143.  * Automatic hashrate report
  144.  *
  145.  * h_print_time - How often, in seconds, should we print a hashrate report if verbose_level is set to 4.
  146.  *                This option has no effect if verbose_level is not 4.
  147.  */
  148. "h_print_time" : 60,
  149.  
  150. /*
  151.  * Output file
  152.  *
  153.  * output_file  - This option will log all output to a file.
  154.  *
  155.  */
  156. "output_file" : "",
  157.  
  158. /*
  159.  * Built-in web server
  160.  * I like checking my hashrate on my phone. Don't you?
  161.  * Keep in mind that you will need to set up port forwarding on your router if you want to access it from
  162.  * outside of your home network. Ports lower than 1024 on Linux systems will require root.
  163.  *
  164.  * httpd_port - Port we should listen on. Default, 0, will switch off the server.
  165.  */
  166. "httpd_port" : 0,
  167.  
  168. /*
  169.  * prefer_ipv4 - IPv6 preference. If the host is available on both IPv4 and IPv6 net, which one should be choose?
  170.  *               This setting will only be needed in 2020's. No need to worry about it now.
  171.  */
  172. "prefer_ipv4" : true,
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!
 
Top