89 lines
4.1 KiB
Plaintext
89 lines
4.1 KiB
Plaintext
/*
|
|
* Number of GPUs that you have in your system. Each GPU will get its own CPU thread.
|
|
*/
|
|
"gpu_thread_num" : 6,
|
|
|
|
/*
|
|
* GPU configuration. You should play around with intensity and worksize as the fastest settings will vary.
|
|
* index - GPU index number usually starts from 0
|
|
* intensity - Number of parallel GPU threads (nothing to do with CPU threads)
|
|
* worksize - Number of local GPU threads (nothing to do with CPU threads)
|
|
* affine_to_cpu - This will affine the thread to a CPU. This can make a GPU miner play along nicer with a CPU miner.
|
|
*/
|
|
"gpu_threads_conf" : [
|
|
{ "index" : 0, "intensity" : 1000, "worksize" : 8, "affine_to_cpu" : false },
|
|
{ "index" : 1, "intensity" : 1000, "worksize" : 8, "affine_to_cpu" : false },
|
|
{ "index" : 2, "intensity" : 1000, "worksize" : 8, "affine_to_cpu" : false },
|
|
{ "index" : 3, "intensity" : 1000, "worksize" : 8, "affine_to_cpu" : false },
|
|
{ "index" : 4, "intensity" : 1000, "worksize" : 8, "affine_to_cpu" : false },
|
|
{ "index" : 5, "intensity" : 1000, "worksize" : 8, "affine_to_cpu" : false },
|
|
],
|
|
|
|
/*
|
|
* Platform index. This will be 0 unless you have different OpenCL platform - eg. AMD and Intel.
|
|
*/
|
|
"platform_index" : 0,
|
|
|
|
/*
|
|
* pool_address - Pool address should be in the form "pool.supportxmr.com:3333". Only stratum pools are supported.
|
|
* wallet_address - Your wallet, or pool login.
|
|
* pool_password - Can be empty in most cases or "x".
|
|
*/
|
|
"pool_address" : "pool.supportxmr.com:3333",
|
|
"wallet_address" : "",
|
|
"pool_password" : "",
|
|
|
|
/*
|
|
* Network timeouts.
|
|
* Because of the way this client is written it doesn't need to constantly talk (keep-alive) to the server to make
|
|
* sure it is there. We detect a buggy / overloaded server by the call timeout. The default values will be ok for
|
|
* nearly all cases. If they aren't the pool has most likely overload issues. Low call timeout values are preferable -
|
|
* long timeouts mean that we waste hashes on potentially stale jobs. Connection report will tell you how long the
|
|
* server usually takes to process our calls.
|
|
*
|
|
* call_timeout - How long should we wait for a response from the server before we assume it is dead and drop the connection.
|
|
* retry_time - How long should we wait before another connection attempt.
|
|
* Both values are in seconds.
|
|
*/
|
|
"call_timeout" : 10,
|
|
"retry_time" : 10,
|
|
|
|
/*
|
|
* Output control.
|
|
* Since most people are used to miners printing all the time, that's what we do by default too. This is suboptimal
|
|
* really, since you cannot see errors under pages and pages of text and performance stats. Given that we have internal
|
|
* performance monitors, there is very little reason to spew out pages of text instead of concise reports.
|
|
* Press 'h' (hashrate), 'r' (results) or 'c' (connection) to print reports.
|
|
*
|
|
* verbose_level - 0 - Don't print anything.
|
|
* 1 - Print intro, connection event, disconnect event
|
|
* 2 - All of level 1, and new job (block) event if the difficulty is different from the last job
|
|
* 3 - All of level 1, and new job (block) event in all cases, result submission event.
|
|
* 4 - All of level 3, and automatic hashrate report printing
|
|
*/
|
|
"verbose_level" : 3,
|
|
|
|
/*
|
|
* Automatic hashrate report
|
|
*
|
|
* h_print_time - How often, in seconds, should we print a hashrate report if verbose_level is set to 4.
|
|
* This option has no effect if verbose_level is not 4.
|
|
*/
|
|
"h_print_time" : 60,
|
|
|
|
/*
|
|
* Built-in web server
|
|
* I like checking my hashrate on my phone. Don't you?
|
|
* Keep in mind that you will need to set up port forwarding on your router if you want to access it from
|
|
* outside of your home network. Ports lower than 1024 on Linux systems will require root.
|
|
*
|
|
* httpd_port - Port we should listen on. Default, 0, will switch off the server.
|
|
*/
|
|
"httpd_port" : 0,
|
|
|
|
/*
|
|
* prefer_ipv4 - IPv6 preference. If the host is available on both IPv4 and IPv6 net, which one should be choose?
|
|
* This setting will only be needed in 2020's. No need to worry about it now.
|
|
*/
|
|
"prefer_ipv4" : true,
|