|
hashgoalPool
|
 |
March 04, 2017, 12:24:23 PM |
|
О каком пуле идет речь?
xcrypto.org Да, как то странно, на xcrypto.org первый блок есть:  а выплат х...й:  имел проблемы в процессоре оплаты, зафиксировал его блок оплачена.  |
|
|
|
|
Sberex
|
|
March 04, 2017, 12:43:28 PM |
|
О каком пуле идет речь?
xcrypto.org Да, как то странно, на xcrypto.org первый блок есть: а выплат х...й: имел проблемы в процессоре оплаты, зафиксировал его блок оплачена. Thank you, there is no need to translate from English to Russian, if it's just Google Translate. |
|
|
|
|
Vov4ik2682
|
|
March 04, 2017, 02:25:28 PM |
|
Выложите кто-то пример Конфиг файла для XMR-Stak-CPU. Заранее благодарен |
|
|
|
ss25
Member
 Offline
Activity: 89
Merit: 10
|
|
March 04, 2017, 03:52:59 PM |
|
на XMR-Stak-CPU тут выкладывали раньше с тестами полистать надо.
xmrMiner у меня этот майнер с опциями -l 6x48 на gtx 460se 768mb дает чуть больше 70 хешей, а обычный ccminer 120.
|
|
|
|
|
|
Sberex
|
|
March 04, 2017, 04:00:41 PM |
|
Выложите кто-то пример Конфиг файла для XMR-Stak-CPU. Заранее благодарен /*
* Number of threads. You can configure them below. Cryptonight uses 2MB of memory, so the optimal setting
* here is the size of your L3 cache divided by 2. Intel mid-to-high end desktop processors have 2MB of L3
* cache per physical core. Low end cpus can have 1.5 or 1 MB while Xeons can have 2, 2.5 or 3MB per core.
*/
"cpu_thread_num" : 4,
/*
* Thread configuration for each thread. Make sure it matches the number above.
* low_power_mode - This mode will double the cache usage, and double the single thread performance. It will
* consume much less power (as less cores are working), but will max out at around 80-85% of
* the maximum performance.
*
* no_prefetch - This mode meant for large pages only. It will generate an error if running on slow memory
* Some sytems can gain up to extra 5% here, but sometimes it will have no difference or make
* things slower.
*
* affine_to_cpu - This can be either false (no affinity), or the CPU core number. Note that on hyperthreading
* systems it is better to assign threads to physical cores. On Windows this usually means selecting
* even or odd numbered cpu numbers. For Linux it will be usually the lower CPU numbers, so for a 4
* physical core CPU you should select cpu numbers 0-3.
*
*/
"cpu_threads_conf" : [
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 0 },
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 1 },
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 2 },
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 3 },
],
/*
* LARGE PAGE SUPPORT
* Lare pages need a properly set up OS. It can be difficult if you are not used to systems administation,
* but the performace results are worth the trouble - you will get around 20% boost. Slow memory mode is
* meant as a backup, you won't get stellar results there. If you are running into trouble, especially
* on Windows, please read the common issues in the README.
*
* By default we will try to allocate large pages. This means you need to "Run As Administrator" on Windows.
* You need to edit your system's group policies to enable locking large pages. Here are the steps from MSDN
*
* 1. On the Start menu, click Run. In the Open box, type gpedit.msc.
* 2. On the Local Group Policy Editor console, expand Computer Configuration, and then expand Windows Settings.
* 3. Expand Security Settings, and then expand Local Policies.
* 4. Select the User Rights Assignment folder.
* 5. The policies will be displayed in the details pane.
* 6. In the pane, double-click Lock pages in memory.
* 7. In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.
* 8. In the Select Users, Service Accounts, or Groups dialog box, add an account that you will run the miner on
* 9. Reboot for change to take effect.
*
* Windows also tends to fragment memory a lot. If you are running on a system with 4-8GB of RAM you might need
* to switch off all the auto-start applications and reboot to have a large enough chunk of contiguous memory.
*
* On Linux you will need to configure large page support "sudo sysctl -w vm.nr_hugepages=128" and increase your
* ulimit -l. To do do this you need to add following lines to /etc/security/limits.conf - "* soft memlock 262144"
* and "* hard memlock 262144". You can also do it Windows-style and simply run-as-root, but this is NOT
* recommended for security reasons.
*
* Memory locking means that the kernel can't swap out the page to disk - something that is unlikey to happen on a
* command line system that isn't starved of memory. I haven't observed any difference on a CLI Linux system between
* locked and unlocked memory. If that is your setup see option "no_mlck".
*/
/*
* use_slow_memory defines our behaviour with regards to large pages. There are three possible options here:
* always - Don't even try to use large pages. Always use slow memory.
* warn - We will try to use large pages, but fall back to slow memory if that fails.
* no_mlck - This option is only relevant on Linux, where we can use large pages without locking memory.
* It will never use slow memory, but it won't attempt to mlock
* never - If we fail to allocate large pages we will print an error and exit.
*/
"use_slow_memory" : "warn",
/*
* NiceHash mode
* nicehash_nonce - Limit the noce to 3 bytes as required by nicehash. This cuts all the safety margins, and
* if a block isn't found within 30 minutes then you might run into nonce collisions. Number
* of threads in this mode is hard-limited to 32.
*/
"nicehash_nonce" : false,
/*
* TLS Settings
* If you need real security, make sure tls_secure_algo is enabled (otherwise MITM attack can downgrade encryption
* to trivially breakable stuff like DES and MD5), and verify the server's fingerprint through a trusted channel.
*
* use_tls - This option will make us connect using Transport Layer Security.
* tls_secure_algo - Use only secure algorithms. This will make us quit with an error if we can't negotiate a secure algo.
* tls_fingerprint - Server's SHA256 fingerprint. If this string is non-empty then we will check the server's cert against it.
*/
"use_tls" : false,
"tls_secure_algo" : true,
"tls_fingerprint" : "",
/*
* 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" : "krb.sberex.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.
* giveup_limit - Limit how many times we try to reconnect to the pool. Zero means no limit. Note that stak miners
* don't mine while the connection is lost, so your computer's power usage goes down to idle.
*/
"call_timeout" : 10,
"retry_time" : 10,
"giveup_limit" : 0,
/*
* 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" : 4,
/*
* 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,
/*
* Output file
*
* output_file - This option will log all output to a file.
*
*/
"output_file" : "",
/*
* 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,
|
|
|
|
|
nezaigor
|
|
March 04, 2017, 04:03:17 PM |
|
Продал Мраи - купил Карбованцы. Приятное вложение. Кстате Криптопия рулит. НА Лайвкоине тоже прикупил.
|
|
|
|
|
Ganlok
Sr. Member
Offline
Activity: 292
Merit: 250
karbo.io
|
|
March 04, 2017, 04:15:55 PM |
|
   В чем соль? Смотреть на ласт блоки. Не мог же крипто-коинс.клуб 2-3 часа кряду ловить такую удачу, или мог? А и да, он почему-то выпал из статистики всех пулов. Он-то есть, точнее, но не на главной, а во вкладке "сеть/мережа/нэтворк". |
█████▄▄██████████▄▄█████
███▄████████████████▄███
████████████████████████
████████████████████████
████████████████████████
████████████████████████
████████████████████████
████████████████████████
████████████████████████
████████████████████████
██▀██████████████████▀██
████▀▀████████████▀▀████ | | | | Ҝ
Ҝ
Ҝ | | | | Ҝ
Ҝ
Ҝ | | · Anonymity by CryptoNote
· Zero premine & instamine
· Low transaction fee |
|
|
|
|
Vov4ik2682
|
|
March 04, 2017, 04:29:19 PM |
|
Выложите кто-то пример Конфиг файла для XMR-Stak-CPU. Заранее благодарен /*
* Number of threads. You can configure them below. Cryptonight uses 2MB of memory, so the optimal setting
* here is the size of your L3 cache divided by 2. Intel mid-to-high end desktop processors have 2MB of L3
* cache per physical core. Low end cpus can have 1.5 or 1 MB while Xeons can have 2, 2.5 or 3MB per core.
*/
"cpu_thread_num" : 4,
/*
* Thread configuration for each thread. Make sure it matches the number above.
* low_power_mode - This mode will double the cache usage, and double the single thread performance. It will
* consume much less power (as less cores are working), but will max out at around 80-85% of
* the maximum performance.
*
* no_prefetch - This mode meant for large pages only. It will generate an error if running on slow memory
* Some sytems can gain up to extra 5% here, but sometimes it will have no difference or make
* things slower.
*
* affine_to_cpu - This can be either false (no affinity), or the CPU core number. Note that on hyperthreading
* systems it is better to assign threads to physical cores. On Windows this usually means selecting
* even or odd numbered cpu numbers. For Linux it will be usually the lower CPU numbers, so for a 4
* physical core CPU you should select cpu numbers 0-3.
*
*/
"cpu_threads_conf" : [
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 0 },
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 1 },
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 2 },
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 3 },
],
/*
* LARGE PAGE SUPPORT
* Lare pages need a properly set up OS. It can be difficult if you are not used to systems administation,
* but the performace results are worth the trouble - you will get around 20% boost. Slow memory mode is
* meant as a backup, you won't get stellar results there. If you are running into trouble, especially
* on Windows, please read the common issues in the README.
*
* By default we will try to allocate large pages. This means you need to "Run As Administrator" on Windows.
* You need to edit your system's group policies to enable locking large pages. Here are the steps from MSDN
*
* 1. On the Start menu, click Run. In the Open box, type gpedit.msc.
* 2. On the Local Group Policy Editor console, expand Computer Configuration, and then expand Windows Settings.
* 3. Expand Security Settings, and then expand Local Policies.
* 4. Select the User Rights Assignment folder.
* 5. The policies will be displayed in the details pane.
* 6. In the pane, double-click Lock pages in memory.
* 7. In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.
* 8. In the Select Users, Service Accounts, or Groups dialog box, add an account that you will run the miner on
* 9. Reboot for change to take effect.
*
* Windows also tends to fragment memory a lot. If you are running on a system with 4-8GB of RAM you might need
* to switch off all the auto-start applications and reboot to have a large enough chunk of contiguous memory.
*
* On Linux you will need to configure large page support "sudo sysctl -w vm.nr_hugepages=128" and increase your
* ulimit -l. To do do this you need to add following lines to /etc/security/limits.conf - "* soft memlock 262144"
* and "* hard memlock 262144". You can also do it Windows-style and simply run-as-root, but this is NOT
* recommended for security reasons.
*
* Memory locking means that the kernel can't swap out the page to disk - something that is unlikey to happen on a
* command line system that isn't starved of memory. I haven't observed any difference on a CLI Linux system between
* locked and unlocked memory. If that is your setup see option "no_mlck".
*/
/*
* use_slow_memory defines our behaviour with regards to large pages. There are three possible options here:
* always - Don't even try to use large pages. Always use slow memory.
* warn - We will try to use large pages, but fall back to slow memory if that fails.
* no_mlck - This option is only relevant on Linux, where we can use large pages without locking memory.
* It will never use slow memory, but it won't attempt to mlock
* never - If we fail to allocate large pages we will print an error and exit.
*/
"use_slow_memory" : "warn",
/*
* NiceHash mode
* nicehash_nonce - Limit the noce to 3 bytes as required by nicehash. This cuts all the safety margins, and
* if a block isn't found within 30 minutes then you might run into nonce collisions. Number
* of threads in this mode is hard-limited to 32.
*/
"nicehash_nonce" : false,
/*
* TLS Settings
* If you need real security, make sure tls_secure_algo is enabled (otherwise MITM attack can downgrade encryption
* to trivially breakable stuff like DES and MD5), and verify the server's fingerprint through a trusted channel.
*
* use_tls - This option will make us connect using Transport Layer Security.
* tls_secure_algo - Use only secure algorithms. This will make us quit with an error if we can't negotiate a secure algo.
* tls_fingerprint - Server's SHA256 fingerprint. If this string is non-empty then we will check the server's cert against it.
*/
"use_tls" : false,
"tls_secure_algo" : true,
"tls_fingerprint" : "",
/*
* 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" : "krb.sberex.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.
* giveup_limit - Limit how many times we try to reconnect to the pool. Zero means no limit. Note that stak miners
* don't mine while the connection is lost, so your computer's power usage goes down to idle.
*/
"call_timeout" : 10,
"retry_time" : 10,
"giveup_limit" : 0,
/*
* 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" : 4,
/*
* 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,
/*
* Output file
*
* output_file - This option will log all output to a file.
*
*/
"output_file" : "",
/*
* 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,
Спасибо. Запустил, увидел хешрейт и выключил  Выдал 75-80 х/с, cpuminer показывает куда больше: 95-100 х/с |
|
|
|
aiwe
Legendary
Offline
Activity: 1750
Merit: 1101
karbo.io
|
|
March 04, 2017, 06:08:18 PM |
|
"cpu_threads_conf" : [
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 0 },
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 1 },
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 2 },
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 3 },
],
нужно чередовать ядра: "cpu_threads_conf" : [
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 0 },
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 2 },
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 4 },
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 6 },
], В чем соль? Смотреть на ласт блоки. Не мог же крипто-коинс.клуб 2-3 часа кряду ловить такую удачу, или мог? А и да, он почему-то выпал из статистики всех пулов. Он-то есть, точнее, но не на главной, а во вкладке "сеть/мережа/нэтворк". если у него значительный перевес по хешрейту то мог, там промышляет какой-то майнер-найсхешовец. Его право, лишь бы не тормозил сетку и не пытался злоупотреблять, надеюсь у него хватит ума. Так откуда пул пропал-то, я не понял? |
████▄▄████████████▄▄████
██▄██████████████████▄██
████████████████████████
████████████████████████
████████████████████████
████████████████████████
████████████████████████
████████████████████████
████████████████████████
████████████████████████
██▀██████████████████▀██
████▀▀████████████▀▀████ | | | | Ҝ
Ҝ
Ҝ | | | | Ҝ
Ҝ
Ҝ | | | | Ҝ
Ҝ
Ҝ | | | | Ҝ
Ҝ
Ҝ |
|
|
|
ss25
Member
Offline
Activity: 89
Merit: 10
|
|
March 04, 2017, 06:40:37 PM |
|
он имел ввиду наверно то что большая разница между хешрейтом сети который показывается тут http://explorer.karbowanec.com/#pools (в 2 раза выше был) и тем который в поле Hash Rate: раздела Network |
|
|
|
|
aiwe
Legendary
Offline
Activity: 1750
Merit: 1101
karbo.io
|
|
March 04, 2017, 08:40:26 PM |
|
он имел ввиду наверно то что большая разница между хешрейтом сети который показывается тут http://explorer.karbowanec.com/#pools (в 2 раза выше был) и тем который в поле Hash Rate: раздела Network а, на главной странице - примерный хешрейт сети судя по текущей сложности, а на странице со списком пулов - их суммарный хешрейт, но нужно учитывать во первых там не все майнеры, а во вторых - повторяю - примерный хешрейт, это примерный хешрейт т.е. очень приблизительная величина которая очень сильно меняется как и сложность |
████▄▄████████████▄▄████
██▄██████████████████▄██
████████████████████████
████████████████████████
████████████████████████
████████████████████████
████████████████████████
████████████████████████
████████████████████████
████████████████████████
██▀██████████████████▀██
████▀▀████████████▀▀████ | | | | Ҝ
Ҝ
Ҝ | | | | Ҝ
Ҝ
Ҝ | | | | Ҝ
Ҝ
Ҝ | | | | Ҝ
Ҝ
Ҝ |
|
|
|
|
farsky
|
|
March 04, 2017, 09:38:15 PM |
|
я не оценил XMR-Stak-CPU. Вульф проще в настройке и давит больше скорость. Расскажите лучше про майнер Вульфа для CPU, вот этот https://bitcointalk.org/index.php?topic=632724в теме загадочно недоступны ссылки на последние версии. Однако автор, судя по скриншотам, добился неплохих успехов. Может быть кто-то может откопать свежий майнер и залить на Мегу ? И еще. Господа, надо что-то предпринимать с курсом карбованца. Судя по сливам, из монеты уходят инвесторы, уставшие ждать. |
Rus fascists: Goran_, mp3.Maniac, Xommy, ivan1975, lovesmayfamilis, Excimer, leonello, Snork1979, be.open, K210, Azrieli.
|
|
|
|
hashgoalPool
|
|
March 05, 2017, 05:29:22 AM |
|
added nicehash port 8888 , diff 25000
stratum+tcp://xcrypto.org:8888
|
|
|
|
|
andrikerch
|
|
March 05, 2017, 06:53:57 AM |
|
Судя по сливам, из монеты уходят инвесторы, уставшие ждать.
Совсем не обязательно им быть инвесторами. После добавления на whattomine.com Карбванец начали майнить те кто как раз ради слива и майнит. Я как раз и ждал что будет падение цены что бы перезакупиться. |
|
|
|
|
|
Burovik99
|
|
March 05, 2017, 07:03:27 AM |
|
Судя по сливам, из монеты уходят инвесторы, уставшие ждать.
Совсем не обязательно им быть инвесторами. После добавления на whattomine.com Карбванец начали майнить те кто как раз ради слива и майнит. Я как раз и ждал что будет падение цены что бы перезакупиться. Может, конечно и майнеры, но судя по количеству продаваемых монет, вряд ли. Больше похоже на выход инвесторов, купивших на уровне 1000-1500 и сейчас фиксирующих прибыль. Да и биток опять же... |
|
|
|
|
|
Buratinos
|
|
March 05, 2017, 08:14:33 AM |
|
я не оценил XMR-Stak-CPU. Вульф проще в настройке и давит больше скорость. Расскажите лучше про майнер Вульфа для CPU, вот этот https://bitcointalk.org/index.php?topic=632724в теме загадочно недоступны ссылки на последние версии. Однако автор, судя по скриншотам, добился неплохих успехов. Может быть кто-то может откопать свежий майнер и залить на Мегу ? И еще. Господа, надо что-то предпринимать с курсом карбованца. Судя по сливам, из монеты уходят инвесторы, уставшие ждать. Я о wolf под ЦПУ давно писал, что майнер не плохой, чего не скажешь о его ГПУ версии... У deva наверняка есть версии по оптимизированней, он ведь ими приторговывает |
|
|
|
|
|
nezaigor
|
|
March 05, 2017, 10:25:14 AM |
|
Нормально все с ценой. Есть хорошая возможность перезакупится.
|
|
|
|
|
|
Iserviceman
|
|
March 05, 2017, 10:28:56 AM |
|
Нормально все с ценой. Есть хорошая возможность перезакупится.
Самое главное на фоне скачков битка к фиату курс более-менее стабильно держится. Насчет закупа - согласен, перспективы есть, поэтому налейте мне в "ложечки", кто не верит |
|
|
|
|
|
fantom1962.
|
|
March 05, 2017, 10:46:49 AM |
|
Нормально все с ценой. Есть хорошая возможность перезакупится.
Если это нормально то что такое плохо?Если динамики роста монеты нет это по определению плохой признак.Ждем выхода нового кошелька и тогда увидим какой тренд будет у монеты. |
|
|
|
|
|
Vov4ik2682
|
|
March 05, 2017, 10:52:49 AM |
|
"cpu_threads_conf" : [
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 0 },
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 1 },
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 2 },
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 3 },
],
нужно чередовать ядра: "cpu_threads_conf" : [
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 0 },
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 2 },
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 4 },
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 6 },
], В смысле, чередовать? У меня 4 ядра, я все их ставлю на майнинг. |
|
|
|
|
