by

Xmr Stak Auto Tune

Xmr Stak Auto Tune 8,9/10 9697 votes

Download

Xmr
  1. Xmr Stak Auto Tuneup
  2. Xmr Stak Auto Tunes
Tuner

Xmr Stak Auto Tuneup

Mar 10, 2018  I present a new utility for you all - XMR-Stak remote monitor A small executable that will read from the XMR-Stak HTTP daemon and upload hashrate data every 30 seconds allowing you to monitor hashrate for multiple rigs or XMR-Stak instances in one place. . affinetocpu - This will affine the thread to a CPU. This can make a GPU miner play along nicer with a CPU miner. Sep 15, 2017  Xmrig is a faster XMR miner in some use cases. Discussion in 'Cryptocurrency Mining and Markets' started by Klee. Free download professional vst plugins downloads. Anyway I swapped the E5-2660's and the 2660's so now it at least gives me the opportunity to compare xmr-stak-cpu with xmrig under Ubuntu 16.04 and its about the same performance. The core auto config seems to work perfectly. Oct 04, 2017  How Intall XMR-STAK-CPU - Monero Mining Tool. I recommend using xmr-stak-cpu, a very fast, cost-effective, open source solution. First off, we will have to install dependencies of the program. We will also have to compile it, so we need software for that, too. Run: sudo apt install libmicrohttpd-dev libssl-dev cmake build-essential libhwloc-dev. Search for: Search Welcome to XMR-Stak XMRStak.com aims to provide you with a place to share and find the best configurations for your AMD & Nvidia Video Cards as well as Intel and AMD Processors. You can read more about XMR-Stak on the official Github page. New Monero ConfigurationsAMD Ryzen 5 2600 w/stock cooler – Continue reading 'XMR-Stak.

Xmr Stak Auto Tunes

  1. // generated by xmr-stak/2.10.7/fd19a5d03/unknown/win/amd-cpu/20
  2. /*
  3. * GPU configuration. You should play around with intensity and worksize as the fastest settings will vary.
  4. * intensity - Number of parallel GPU threads (nothing to do with CPU threads)
  5. * worksize - Number of local GPU threads (nothing to do with CPU threads)
  6. * affine_to_cpu - This will affine the thread to a CPU. This can make a GPU miner play along nicer with a CPU miner.
  7. * strided_index - switch memory pattern used for the scratchpad memory
  8. * 3 = chunked memory, chunk size based on the 'worksize'
  9. * required: intensity must be a multiple of worksize
  10. * 2 = chunked memory, chunk size is controlled by 'mem_chunk'
  11. * required: intensity must be a multiple of worksize
  12. * 1 or true = use 16 byte contiguous memory per thread, the next memory block has offset of intensity blocks
  13. * (for cryptonight_v8 and monero it is equal to strided_index = 0)
  14. * 0 or false = use a contiguous block of memory per thread
  15. * mem_chunk - range 0 to 18: set the number of elements (16byte) per chunk
  16. * this value is only used if 'strided_index' 2
  17. * element count is computed with the equation: 2 to the power of 'mem_chunk' e.g. 4 means a chunk of 16 elements(256 byte)
  18. * unroll - allow to control how often the POW main loop is unrolled; valid range [1;128) - for most OpenCL implementations it must be a power of two.
  19. * comp_mode - Compatibility enable/disable the automatic guard around compute kernel which allows
  20. * to use an intensity which is not the multiple of the worksize.
  21. * If you set false and the intensity is not multiple of the worksize the miner can crash:
  22. * in this case set the intensity to a multiple of the worksize or activate comp_mode.
  23. * interleave - Controls the starting point in time between two threads on the same GPU device relative to the last started thread.
  24. * This option has only an effect if two compute threads using the same GPU device: valid range [0;100]
  25. * 40 = each working thread waits until 40% of the hash calculation of the previously started thread is finished
  26. * [
  27. * { 'index' : 0, 'intensity' : 1000, 'worksize' : 8, 'affine_to_cpu' : false,
  28. * 'strided_index' : true, 'mem_chunk' : 2, 'unroll' : 8, 'comp_mode' : true,
  29. * },
  30. * If you do not wish to mine with your AMD GPU(s) then use:
  31. * null,
  32. // gpu: Caicos compute units: 2
  33. // memory:192 192 384 MiB (used per thread max per alloc total free)
  34. 'intensity' : 40, 'worksize' : 8,
  35. 'affine_to_cpu' : false, 'strided_index' : 0, 'mem_chunk' : 2,
  36. 'unroll' : 1, 'comp_mode' : true, 'interleave' : 40
  37. * number of rounds per intensity performed to find the best intensity settings
  38. * WARNING: experimental option
  39. * 0 = disable auto tuning
  40. * 10 or higher = recommended value if you don't already know the best intensity
  41. 'auto_tune' : 0,
  42. /*
  43. * Platform index. This will be 0 unless you have different OpenCL platform - eg. AMD and Intel.
  44. 'platform_index' : 1,