JerryMiner-XMR

[Yoda]

Добавлю немного статистики

i3-4170 - 96 хешей против 82 xmr-stak'а

 

[rgusev]

Народ. Вы как мереете то? Вы что, только в автомате? А в ручную поиграться ядрами не судьба? stak по дефолту в щадящем режиме работает.

 

[rgusev]

i7-4770

При запуске в дефолте, сабж прибыльней на 5-10 хешей.

Если настраивать в ручную, то stak далеко впереди.

Запускаем stak в двух вариантах.

1 - 4 ядра.

2. - 2 или 3 ядра.

Получаем 220 + 150.

Один JerryMiner-XMR больше 240 не вытягивает. 

При попытке запустить 2 копию, хешрейт падает в обоих копиях запущенной программы.

 

Вот скрин. xmr-stak-cpu-win64 майнер.  Две копии.  4 + 3 ядра. Машина проработала пару часов. Перед уходом перегрузил ее, почитстил память. 

До таких скоростей разгоняется не всегда.

Скрин сделан по TeamViewer

Изменено 9 ноя 2017, 19:22 пользователем rgusev
Добавлен скриншот

[rgusev]

P.S.

Вообще говоря, впервые вижу такие скорости. Может потому что сейчас запущено через Stratum Proxy  с прошлой странички.

https://forum.bits.media/index.php?/topic/55512-jerryminer-xmr/&do=findComment&comment=973987

Поэтому как доказанное будем считать 200/220 + 140/160. Напрямую с дварфпулом так показывало.

Это моя рабочая машина. Там ещё 2 nVidia карточки стоят и тоже майнят.

Вообще у меня 2 рига на картах. Один на Радеонах, второй на нВидиа.

Это так,.. по принципу "если есть, то почему не использовать?"

По видюхам сразу проседает при подключении TeamViewer, а в чистую 149 +130, примерно так.

Без разгона. Карты халявные. Поснимал с офисных компов при поставке.

 

Изменено 9 ноя 2017, 19:44 пользователем rgusev

[_Jerry]

5 часов назад, rgusev сказал:

i7-4770

При запуске в дефолте, сабж прибыльней на 5-10 хешей.

Если настраивать в ручную, то stak далеко впереди.

Запускаем stak в двух вариантах.

1 - 4 ядра.

2. - 2 или 3 ядра.

Получаем 220 + 150.

Один JerryMiner-XMR больше 240 не вытягивает. 

При попытке запустить 2 копию, хешрейт падает в обоих копиях запущенной программы.

 

Вот скрин. xmr-stak-cpu-win64 майнер.  Две копии.  4 + 3 ядра. Машина проработала пару часов. Перед уходом перегрузил ее, почитстил память. 

До таких скоростей разгоняется не всегда.

Вы бы привели конфиги JerryMiner и конфиг xmr-stack-cpu.

Также лог с теста. Так что то трудно сказать.

---

Вообще скорей всего у вас где то ошибка. Вы говорите что запускаете в 6-7 ядер, но это больше чем ваш L3/2мб , ведь для i7-4770 он составляет 8мб, то есть 4 потока максимум.

Еще: в моем майнере есть воркеры xmr-stak, то есть кусок кода из их исходников(там всего 3и функции), скомпилированные под разные платформы. Таким образом работать медленнее xmr-stak мой майнер не может(покрайней мере в два раза уж точно), если конечно не задать неверные настройки. 

Изменено 9 ноя 2017, 22:16 пользователем _Jerry

[_Jerry]

5 часов назад, rgusev сказал:

Получаем 220 + 150.

 

3 часа назад, rgusev сказал:

Поэтому как доказанное будем считать 200/220 + 140/160.

 

5 часов назад, rgusev сказал:

 

 

3 часа назад, rgusev сказал:

 

А где на ваших скринах такие цифры? Я вижу также ~240 хешей/сек сумма с обоих процессов.

Изменено 9 ноя 2017, 22:47 пользователем _Jerry

[xxx7]

на e5 2660 v2 потестировать бы.10 ядер 20 кеш.соответственно и потоков в майнере будет 20 же?

[rgusev]

@_Jerry 

Это одна машина на обоих скринах.

Вот более привычная картина.

 

Конфиги stak.

Скрытый текст

/*
 * 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 -    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.
 *
 * On the first run the miner will look at your system and suggest a basic configuration that will work,
 * you can try to tweak it from there to get the best performance.
 *
 * A filled out configuration should look like this:
 * "cpu_threads_conf" :
 * [
 *      { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 0 },
 *      { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 1 },
 * ],
 */
"cpu_thread_num" : 4,
"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 },

],
/*
 * 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" : true,

/*
 * Manual hardware AES override
 *
 * Some VMs don't report AES capability correctly. You can set this value to true to enforce hardware AES or
 * to false to force disable AES or null to let the miner decide if AES is used.
 *
 * WARNING: setting this to true on a CPU that doesn't support hardware AES will crash the miner.
 */
"aes_override" : null,

/*
 * 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".
 *
 * We feature pools up to 1MH/s. For a more complete list see M5M400's pool list at www.moneropools.com
 */
"pool_address" : "172.20.66.23:2222",
"wallet_address" : "My_CPU_1",
"pool_password" : "x",

/*
 * 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,

/*
 * Daemon mode
 *
 * If you are running the process in the background and you don't need the keyboard reports, set this to true.
 * This should solve the hashrate problems on some emulated terminals.
 */
"daemon_mode" : true,

/*
 * 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,

 

 

Скрытый текст

/*
 * 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 -    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.
 *
 * On the first run the miner will look at your system and suggest a basic configuration that will work,
 * you can try to tweak it from there to get the best performance.
 *
 * A filled out configuration should look like this:
 * "cpu_threads_conf" :
 * [
 *      { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 0 },
 *      { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 1 },
 * ],
 */
"cpu_thread_num" : 3,
"cpu_threads_conf" :
[
    { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 1 },
    { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 3 },
    { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 5 },
],
/*
 * 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" : true,

/*
 * Manual hardware AES override
 *
 * Some VMs don't report AES capability correctly. You can set this value to true to enforce hardware AES or
 * to false to force disable AES or null to let the miner decide if AES is used.
 *
 * WARNING: setting this to true on a CPU that doesn't support hardware AES will crash the miner.
 */
"aes_override" : null,

/*
 * 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".
 *
 * We feature pools up to 1MH/s. For a more complete list see M5M400's pool list at www.moneropools.com
 */
"pool_address" : "172.20.66.23:2222",
"wallet_address" : "My_CPU_2",
"pool_password" : "x",

/*
 * 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,

/*
 * Daemon mode
 *
 * If you are running the process in the background and you don't need the keyboard reports, set this to true.
 * This should solve the hashrate problems on some emulated terminals.
 */
"daemon_mode" : true,

/*
 * 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,

 

Изменено 10 ноя 2017, 09:43 пользователем rgusev

[rgusev]

10 часов назад, _Jerry сказал:

А где на ваших скринах такие цифры? Я вижу также ~240 хешей/сек сумма с обоих процессов.

я и писал что впервые такое вижу. (вероятно из-за ошибки с прокси. те самые false в поддержке эмулации найсхэш)

[MorganKZ]

Could not allocate memory(large page)

Добавлял пользователя Admin и даже группу Администраторы, не помогает.

__last-console.txt

[MorganKZ]

По времени суток если прога сама ставить приоритет процессу, то будет вне конкуренции, Народный Miner!

У кого на работе оставлен комп включенный, пускай пахает за Админа .

 

По расписанию можно конечно создать конфиг файл для майнера через батник, где меняется приоритеты. Но хотелось бы чтоб такая функция имела прога

Изменено 15 ноя 2017, 09:25 пользователем MorganKZ

[karabas]

Версия для  Linux планируется?

[_Jerry]

20 часов назад, MorganKZ сказал:

Could not allocate memory(large page)

Выполните что тут написано https://docs.microsoft.com/ru-ru/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows

Также запускать надо от администратора

20 часов назад, MorganKZ сказал:

По времени суток если прога сама ставить приоритет процессу, то будет вне конкуренции, Народный Miner!

У кого на работе оставлен комп включенный, пускай пахает за Админа .

 

По расписанию можно конечно создать конфиг файл для майнера через батник, где меняется приоритеты. Но хотелось бы чтоб такая функция имела прога

Я думаю лучше это делать сторонними программами.

Например Auto it

6 часов назад, karabas сказал:

Версия для  Linux планируется?

Пока нет.

Но вы можете запустить под wine(я не пробовал, но думаю что запустится).

[MorganKZ]

Я майню уже 6 часов, в начале нормально было, а потом перестал майнится на пул.

Как будто devfee 96%, Usertime 4%.

 

[_Jerry]

1 час назад, MorganKZ сказал:

Я майню уже 6 часов, в начале нормально было, а потом перестал майнится на пул.

Как будто devfee 96%, Usertime 4%.

Неясно. То есть 6 часов майнилось нормально, а потом перестало?

Как долга майнер простаивал?

Приведите всю консоль(например на  https://pastebin.com )

 

[rgusev]

@_Jerry 

С утра было нечто похожее. Судя по скрину, в то же время.
Перевёл на другой пулл, отключив прокси. Разбираться просто не стал. Это тестовый комп. Там i7 и 2 nVidia карточки. Я на нём пробиваю пулы, тестю сервисы  т.д.

Это кстати с него скрины выше были. Мой рабочий комп на работе.

[_Jerry]

В 17.11.2017 в 02:46, rgusev сказал:

С утра было нечто похожее. Судя по скрину, в то же время.
Перевёл на другой пулл, отключив прокси. Разбираться просто не стал. Это тестовый комп. Там i7 и 2 nVidia карточки. Я на нём пробиваю пулы, тестю сервисы  т.д.

Это кстати с него скрины выше были. Мой рабочий комп на работе.

Копируйте если вам не трудно всю консоль, если такое повторится. Это поможет мне определить в чем возможная ошибка и исправить в след. версии.

---

Вообще в майнере не проверяется проверка ответов пула. Только закрытие сокета( и то без кипалайв, и если на сервере сокет отвалится без сообщения о закрытии будет ждать до первого write(то есть до  первого найденого хеша).

Самый худший вариант если на сервере обработчики с клиента снимутся а сокет вообще не закроется, тогда майнер будет впустую работать до планового рестарта на дев фи.

---

В будщих версиях я добавлю проверку ответа на сообщения, а также кипалайв уровня statum.

Изменено 20 ноя 2017, 15:02 пользователем _Jerry

[tOrrerO]

Автор, не хотите перевыложить программу с другим пулом для Dev time?  Найсхеш то не скоро очухается видимо.

[_Jerry]

7 часов назад, tOrrerO сказал:

Автор, не хотите перевыложить программу с другим пулом для Dev time?  Найсхеш то не скоро очухается видимо.

Там всеравно несущественная сумма.

Я уже сразу след версию выложу.

[_Jerry]

Up.

Beta.

https://jerrywm.github.io/xmr/

 

Пожайлуйста сообщите ваши результаты тестирования(__last_console.log).

 

Изменено 13 дек 2017, 13:51 пользователем _Jerry

[Vladshee]

Реально, расписания не хватает :(

[_Jerry]

В 1/31/2018 в 23:01, Vladshee сказал:

Реально, расписания не хватает :(

?

[Vladshee]

повесил к хренам удаленную тачку (i7-6950X, 64GB ram) дважды, второй раз намертво

[_Jerry]

12 часа назад, Vladshee сказал:

повесил к хренам удаленную тачку (i7-6950X, 64GB ram) дважды, второй раз намертво

 

Попробуйте конфиг (предполагаю что гипертрединг включен) (сохранить в system.json)

Цитата

{
    "process_list": [
        {
            "priority": "NORMAL_PRIORITY_CLASS",
            "bind_cpu": "auto",
            "thread_list": [
                {
                    "worker_path": "x64/worker-jerry_x64_aesni_v2.bin",
                    "count": 13,
                    "bind_cpu": "auto",
                    "priority": "THREAD_PRIORITY_NORMAL",
                    "additional_mode": false,
                    "use_aesni": true,
                    "use_prefetch": false
                }
            ]
        }
    ]
}

 

Изменено 10 мар 2018, 10:34 пользователем _Jerry

[tOrrerO]

Добрый вечер, а Ваш последний майнер будет работать в новой сети XMR?

И вопрос по прокси-серверу, тоже нужно менять или можно старый оставить?