Bitcoin Forum
November 17, 2018, 03:26:44 AM *
News: Latest Bitcoin Core release: 0.17.0 [Torrent].
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 [11] 12 13 »  All
  Print  
Author Topic: [ANN] TeamRedMiner - Optimized Win/Linux AMD GPU Miner for lyra2z and phi2  (Read 10190 times)
420sam
Newbie
*
Offline Offline

Activity: 8
Merit: 0


View Profile
November 02, 2018, 03:58:49 PM
 #201

I am getting a lot of shares rejected on Nicehack with the message "Error code: 2 - Job not found"

Hi! I’m guessing you’re talking about CNv8? Awesome if we keep the questions for CNv8 in the separate ann thread in the future, but no worries this time:

Nicehash mining is a little problematic with CN. Calculating a round of hashes for CN takes > 1 sec. For other hash functions numbers in a few ms are more common. So, CN has a much higher probability of your hashes being stale when the gpu job completes. For e.g. direct xmr mining, with a long block time, pools are generally nice about accepting shares for both the current and the previous pool job, so it doesn’t matter much if you got a new job 0.5 secs before you found a share.

For nicehash, this isn’t true. They can throw you around between client orders every 5 secs and are generally more picky with stale shares. A better way to handle nicehash is to abort ongoing gpu work when a new job comes in and start on the new job instead. This means you will throw away precious time on the gpu instead though whenever a job switch occurs, so it’s not 100% sure you’ll be better off anyway.

We have abort support but have not enabled it yet. Bottom line is that nicehash is problematic, we support mining there but you will take a hit in your poolside hashrate compared to normal/direct coin mining.



Thank you for the explanation. I think 0.3.6 is performing a little better with this, but maybe it's too early to tell after only running the miner for 4 hours. I would appreciate any improvement you can make in this area. Do you have any suggestions of how I can automatically convert my GPU power into BTC other than Nicehack?
1542425204
Hero Member
*
Offline Offline

Posts: 1542425204

View Profile Personal Message (Offline)

Ignore
1542425204
Reply with quote  #2

1542425204
Report to moderator
1542425204
Hero Member
*
Offline Offline

Posts: 1542425204

View Profile Personal Message (Offline)

Ignore
1542425204
Reply with quote  #2

1542425204
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1542425204
Hero Member
*
Offline Offline

Posts: 1542425204

View Profile Personal Message (Offline)

Ignore
1542425204
Reply with quote  #2

1542425204
Report to moderator
FFI2013
Hero Member
*****
Offline Offline

Activity: 815
Merit: 502


JOIN THE NEXT MEGATREND IN CRYPTO!


View Profile
November 03, 2018, 12:50:59 AM
 #202

Hello dear developers! I've installed this miner and it works perfectly stable, provides good hashrate. But dev fee is bearish... Please reduce it to 1-1.5% for cn8 and 1.5-2% for other algos. You will see - a lot of people will begun to use your miner, it's very important for community

Hi!

Thank you for using the miner!

I really don't want to get into any prolonged argument around our choice of dev fee(s). I would like to say this though to try to paint a better picture: I don't think people understand the difference between our work and that of other miner devs working in OpenCL.

In the ongoing fpga group buy, the established consensus around the dev fee is 4%. No one complaining. Fpga bitstream work is even more tedious, but with the workflow we use it's very much a valid comparison. I can easily spend a whole day looking at a section of raw asm code trying to optimize away a single four-cycle instruction in an inner loop, many times not even knowing if it's worth it or not before I actually succeed doing so. We design and implement the kernels bottom up with as high mechanical sympathy for the hardware as possible, not in high-level code hoping the compiler will do that job well enough for us. A bigger algo can easily take month(s) before we deem it ready for release.

Not all algos will have a big upside with this approach. Many times the compilers do a fantastic job of producing good code. Those algos won't be implemented in this miner, there's no point. For the ones we do spend time on, we are expecting to see a considerable boost that clearly justifies the dev fee from the miner's bottom line perspective. Hence, you should still earn more with our miner after the dev fee, with higher hashrate, lower power draw, or both. If you don't, then I personally don't think you should use this miner.

With the higher dev fee, I also think you can expect and demand a higher level of support service. We're two devs and we're trying as hard as we can to be on the ball for all issues in our ANN threads. God knows how many PMs I've sent the last 2-3 days.

In the end, I respect everyone's free choice in this regard. If you feel that no, I have an issue with giving away 2.5-3% of my hashrate to closed source software devs, even though I might earn less in the end, no one can say you're wrong to do so, it's your choice. However, that respect has to be a two-way street.

Hence, arguing us to slash our petty income from this with -50% because it's "important to the community" isn't really a valid argument imho. If you think about it we're talking about +1.54% for you, -50% for us. In my opinion, the truly most important part for the community is to have the same quality of miners that the big private farms do, and you won't be getting that unless there is enough upside to go public. Even then, it's barely worth it, especially when taking the risk of hacked miners and ripped kernels into account. I can assure you, we're not getting rich from this. I would be way better off chasing down high-end IT consultant gigs instead. I choose to do it instead of more lucrative work because it's fun. The Claymore eth days are long gone.



What gets me is it's been proven that claymore has gotten rich just off the eth miner and as soon as someone goes around his dev fee which he has refused to drop down people start calling him a thief and a scumbag kinda funny isn't here your developing one of the best miners for other algos for AMD which hasn't seen as much love as nvidia lately and people are already starting to bitch about the fee well don't use it or code your own miner if you don't like it, I'm happy with the miner and updates and have no problem with the 3% cause there is either no phi2 amd support or the miner sucks

|


      █████████████▅▄
     ██████████████▅▄
                  ██▆
                   ███
                   ███
                   ███
                   ███
                   ███
                   ███
                   ███
                   ███
                  ███
 ██████████████████▀
██████████████████▀



 ███████████
█████████████




█████████████
█████████████




█████████████
 ███████████



   ▆████████████████
 ▆▆████████████████
███▀
███
███
███▄
 ▀▀███████████████▆▄
  ▀███████████████▅▄
                 ▀███
                  ███
                  ███
                ▄████
 █████████████████▀▀
 █████████████████▀



███
███
███
███
███
███
███
███
███
███
███
███
███
███



   ▆███████████
 ▆▆███████████
███▀
███
███
███
███
███
███
███
███
███▄
 ▀▀█████████████
  ▀█████████████



   ▆████████████▆
 ▆▆█████████████▆▆
███▀             ▀███
███               ███
███               ███
███               ███
███               ███
███               ███
███               ███
███               ███
███               ███
███▄             ▄███
 ▀▀███████████████▀▀
  ▀███████████████▀
|
keksik
Newbie
*
Offline Offline

Activity: 91
Merit: 0


View Profile
November 03, 2018, 05:34:49 PM
 #203

my cards
core is for all cards 1200/900mV, mem is or each cards below:

1 XTR 8G Hynix 2200 H5GQ8H24MJR
2 XTR 8G Hynix 75,4 2225 H5GQ8H24MJR
3 GIGABYTE RX 580 GAMING 4 GB  Hynix 76.1 2000 H5GC4H24AJR
4 XFX RX 580 GTS XXX 8 GB Samsung 73.8 2025 K4G80325FB
5 GIGABYTE RX 580 GAMING 8 GB Hynix 74.4 2200 H5GC8H24MJR
6 GIGABYTE RX 580 GAMING 8 GB Hynix 78.2 2200 H5GC8H24MJR
7 GIGABYTE RX 580 GAMING 4 GB Hynix 73.9 2000 H5GC4H24AJR
8 GIGABYTE RX 580 GAMING 4 GB Hynix 71,5 2000 H5GC4H24AJR
9 GIGABYTE RX 580 GAMING 4 GB Hynix 75.8 2000 H5GC4H24AJR
10 GIGABYTE RX 580 GAMING 4 GB Hynix 77.2 1975 H5GC4H24AJR
11 Sapphire PULSE RX 580 8 GB Samsung 76.3 2050 K4G80325FB
12 GIGABYTE AORUS RX 580 8 GB Hynix 71,3 2100 H5GC8H24MJR

my stats for Phi2 - lux

my bat file
teamredminer.exe -a phi2 -o stratum+tcp://eu.bsod.pw:11518 -u wallet -p c=LUX -d 0,1,2,3,4,5,6,7,8,9,10,11

my results are
approx 5mhs,so for 12gpu 60.4Mhs.

my bat lyra2z
teamredminer.exe -a lyra2z -o stratum+tcp://eu.lyra2z.com:4555 -u PEgBKYxM2Njd47dxkbMFR7eHMacTuMDCbf.12rig -p c=ACM -d 0,1,2,3,4,5,6,7,8,9,10,11

my results are
approx 3-3.2mhs per card,so for 12gpu 38.17Mhs.

anyone got better results? if yes,please share your setup.thx
peteris-apse
Newbie
*
Offline Offline

Activity: 83
Merit: 0


View Profile
November 04, 2018, 11:06:28 AM
 #204

7x vega 56 reference cards rig. 1408/875 1100/875

lyra2z 40mhs 1200w from wall
phi2 65mhs 1150w from wall

lyra2z acm mining at the moment could be more profitable than xmr mining, but i had some wierd stuff with acm mining so i am sticking with xmr.
todxx
Member
**
Offline Offline

Activity: 78
Merit: 25


View Profile
November 04, 2018, 08:37:44 PM
 #205

my cards
core is for all cards 1200/900mV, mem is or each cards below:

1 XTR 8G Hynix 2200 H5GQ8H24MJR
2 XTR 8G Hynix 75,4 2225 H5GQ8H24MJR
3 GIGABYTE RX 580 GAMING 4 GB  Hynix 76.1 2000 H5GC4H24AJR
4 XFX RX 580 GTS XXX 8 GB Samsung 73.8 2025 K4G80325FB
5 GIGABYTE RX 580 GAMING 8 GB Hynix 74.4 2200 H5GC8H24MJR
6 GIGABYTE RX 580 GAMING 8 GB Hynix 78.2 2200 H5GC8H24MJR
7 GIGABYTE RX 580 GAMING 4 GB Hynix 73.9 2000 H5GC4H24AJR
8 GIGABYTE RX 580 GAMING 4 GB Hynix 71,5 2000 H5GC4H24AJR
9 GIGABYTE RX 580 GAMING 4 GB Hynix 75.8 2000 H5GC4H24AJR
10 GIGABYTE RX 580 GAMING 4 GB Hynix 77.2 1975 H5GC4H24AJR
11 Sapphire PULSE RX 580 8 GB Samsung 76.3 2050 K4G80325FB
12 GIGABYTE AORUS RX 580 8 GB Hynix 71,3 2100 H5GC8H24MJR

my stats for Phi2 - lux

my bat file
teamredminer.exe -a phi2 -o stratum+tcp://eu.bsod.pw:11518 -u wallet -p c=LUX -d 0,1,2,3,4,5,6,7,8,9,10,11

my results are
approx 5mhs,so for 12gpu 60.4Mhs.

my bat lyra2z
teamredminer.exe -a lyra2z -o stratum+tcp://eu.lyra2z.com:4555 -u PEgBKYxM2Njd47dxkbMFR7eHMacTuMDCbf.12rig -p c=ACM -d 0,1,2,3,4,5,6,7,8,9,10,11

my results are
approx 3-3.2mhs per card,so for 12gpu 38.17Mhs.

anyone got better results? if yes,please share your setup.thx

Hi keksik,

You might want to try running linux on your rig.  Polaris hashrates for lyra2z/phi2 under linux tend to be better than under windows due to limitations of the windows drivers.
Getting your clocks/voltages configured right under linux can be a challenge.  Most users usually just bios mod them so they are correct right off the bat with no need for tuning inside of linux.
bbvedf
Jr. Member
*
Offline Offline

Activity: 168
Merit: 8


View Profile WWW
November 05, 2018, 01:06:04 PM
 #206

my cards
core is for all cards 1200/900mV, mem is or each cards below:

1 XTR 8G Hynix 2200 H5GQ8H24MJR
2 XTR 8G Hynix 75,4 2225 H5GQ8H24MJR
3 GIGABYTE RX 580 GAMING 4 GB  Hynix 76.1 2000 H5GC4H24AJR
4 XFX RX 580 GTS XXX 8 GB Samsung 73.8 2025 K4G80325FB
5 GIGABYTE RX 580 GAMING 8 GB Hynix 74.4 2200 H5GC8H24MJR
6 GIGABYTE RX 580 GAMING 8 GB Hynix 78.2 2200 H5GC8H24MJR
7 GIGABYTE RX 580 GAMING 4 GB Hynix 73.9 2000 H5GC4H24AJR
8 GIGABYTE RX 580 GAMING 4 GB Hynix 71,5 2000 H5GC4H24AJR
9 GIGABYTE RX 580 GAMING 4 GB Hynix 75.8 2000 H5GC4H24AJR
10 GIGABYTE RX 580 GAMING 4 GB Hynix 77.2 1975 H5GC4H24AJR
11 Sapphire PULSE RX 580 8 GB Samsung 76.3 2050 K4G80325FB
12 GIGABYTE AORUS RX 580 8 GB Hynix 71,3 2100 H5GC8H24MJR

my stats for Phi2 - lux

my bat file
teamredminer.exe -a phi2 -o stratum+tcp://eu.bsod.pw:11518 -u wallet -p c=LUX -d 0,1,2,3,4,5,6,7,8,9,10,11

my results are
approx 5mhs,so for 12gpu 60.4Mhs.

my bat lyra2z
teamredminer.exe -a lyra2z -o stratum+tcp://eu.lyra2z.com:4555 -u PEgBKYxM2Njd47dxkbMFR7eHMacTuMDCbf.12rig -p c=ACM -d 0,1,2,3,4,5,6,7,8,9,10,11

my results are
approx 3-3.2mhs per card,so for 12gpu 38.17Mhs.

anyone got better results? if yes,please share your setup.thx

I do not have a rig itself. I have running 4x Sapphire RX580 8Gb on a conventional PC, under W10 (in my case it is mandatory).

My numbers are not very different from yours. Slightly less than 5mhs in PHI2 (pickaxe pool). Tuning with OverdriveNTool: Core 1220/910, memory 300/800, fan 576/2280. Hwinfo GPU chip power wattage, 90w each approx.

I do not see much difference in performance/stability between the beta version and the stable ones.

Regards!


NCarter84
Newbie
*
Offline Offline

Activity: 20
Merit: 0


View Profile
November 07, 2018, 01:24:49 AM
 #207

What which drivers are we supposed to be using with Windows? amdgpu-pro drivers???

Is that 18.5.1? 18.6? 18.10??
kerney666
Member
**
Online Online

Activity: 126
Merit: 11


View Profile
November 07, 2018, 01:47:13 AM
 #208

What which drivers are we supposed to be using with Windows? amdgpu-pro drivers???

Is that 18.5.1? 18.6? 18.10??

Adrenaline 18.6.1 is our standard driver used for testing. Works well across the board!
NCarter84
Newbie
*
Offline Offline

Activity: 20
Merit: 0


View Profile
November 07, 2018, 05:26:26 PM
 #209

What which drivers are we supposed to be using with Windows? amdgpu-pro drivers???

Is that 18.5.1? 18.6? 18.10??

Adrenaline 18.6.1 is our standard driver used for testing. Works well across the board!

Okay - Haven't been able to get it to run on one of my rigs - but that rig has a PIA card... So, might be the issue. I'll test it on another rig tonight maybe... I'll ensure 18.6.1 drivers are installed.
todxx
Member
**
Offline Offline

Activity: 78
Merit: 25


View Profile
November 08, 2018, 03:42:55 AM
 #210

Team Red Miner v0.3.7 released

https://github.com/todxx/teamredminer/releases

Changes in v0.3.7

  • Redesigned GPU initialization, should now be less error prone.
  • Added clean shutdown to reduce driver/GPU crashes.
  • Added staggered GPU start-up to reduce GPU crashes.
  • Added CPU verification for CNv8 and associated --no_cpu_check option.
  • Fixed crash on pool authentication error.
  • Added --pool_broken_rpc work-around option for pools that violate json rpc spec.
  • Added option to reorder by PCIe bus numbers.
  • Added --list_devices option to show available devices.
  • Added changed stats formatting to indicate which numbers are accepted/rejected/hw-error shares.
  • Added uptime to stats.

There are no changes to lyra2z and phi2 in this version.
There are however a few nice general features like uptime, and bus reordering that might be relevant to lyra2z/phi2 users.
cryptomanman
Newbie
*
Offline Offline

Activity: 23
Merit: 0


View Profile
November 08, 2018, 07:10:26 AM
 #211

Just want to say thanks to the devs! With the newest version, all my 0 H/s problems are resolved!

I'm getting approx 8-12% increase over xmr-stak on all models of my RX cards.

I will say it seems a little less forgiving of poor network conditions (high ping times, flaky wifi, etc.) and it would be really nice to have failover for pools.

But again, thanks!
todxx
Member
**
Offline Offline

Activity: 78
Merit: 25


View Profile
November 08, 2018, 09:21:22 AM
 #212

Just want to say thanks to the devs! With the newest version, all my 0 H/s problems are resolved!

I'm getting approx 8-12% increase over xmr-stak on all models of my RX cards.

I will say it seems a little less forgiving of poor network conditions (high ping times, flaky wifi, etc.) and it would be really nice to have failover for pools.

But again, thanks!

Thanks cryptomanman!  It's so nice to hear that all of our hard work over the last week is helping!
Adding pool failover is on our list, and so is detecting network issues and trying to resolve them a bit earlier.
We've spent most of the last week focusing on getting the miner stable for the users with the 0h/s errors and GPU crashes, but hopefully after this release we can focus on adding some more functionality to the miner.
bbvedf
Jr. Member
*
Offline Offline

Activity: 168
Merit: 8


View Profile WWW
November 08, 2018, 09:53:40 AM
 #213

Thanks dev. I'll give it a try. TeamRedMiner is cool ... Grin
peteris-apse
Newbie
*
Offline Offline

Activity: 83
Merit: 0


View Profile
November 08, 2018, 10:19:44 PM
 #214

yes, thanks! lyra2z, then phi2 and now excelent cnv8 miner. you gave hope back for my team red cards.
freevivone
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
November 08, 2018, 10:34:19 PM
 #215

http://I am very satisfied
I get with vega 64 1950h srb 1.6.8
 TeamRedMiner 2090h
and vega 56 1850h srb
TeamRedMiner 2060h
scryptr
Legendary
*
Offline Offline

Activity: 1512
Merit: 1002



View Profile WWW
November 08, 2018, 10:37:33 PM
 #216

THE TEAMREDMINER MAKES VEGAS PERFORM--

My RX Vega 64 cards hit 2kH/s right away, as soon as I launched the miner!  No "jumping through hoops" with Windows reboots, etc.  A small amount of tuning was required; I did need to adjust the clocks.  I mine on Linux, and my hashrate increased 700+ H/s per card from what I was getting with XMR-Stak.  I started using the miner yesterday, and updated to v0.3.7 today.

I think the console output is more easily read with v0.3.7.  Overall good results, but the rejects are at about 0.5%.  Not terrible, but combined with the dev fee, it is a noticable chunk.  Any suggestions?

Thank you for the mining engine.  Please put the dev fee to good use, I am sure that improvement is still possible.       --scryptr


TIPS:  BTC - 1Fs4uZ6a9ABYBTaHGUfqcwCQmeBRxkKRQT    DASH - XrK81tW31SLsVvZ2WX9VhTjpT6GXJPLdbQ
          ETH - 0x8a42dfAE53612E98daf8614bFA402f3DcD0546Fa    LTC - MKUHfUmRrJUQvELxzajhVaLE5uTPxU2bRK
          SCRYPTR'S NOTEBOOK: https://bitcointalk.org/index.php?topic=5035515.msg46035530#msg46035530  MERIT is appreciated, also.  Thanks!
Bojcha
Hero Member
*****
Offline Offline

Activity: 814
Merit: 500



View Profile
November 09, 2018, 12:57:15 AM
 #217

Can you explain what exactly is 14+16 or 14-14?
scryptr
Legendary
*
Offline Offline

Activity: 1512
Merit: 1002



View Profile WWW
November 09, 2018, 01:26:09 AM
 #218

Can you explain what exactly is 14+16 or 14-14?

IT IS AN INTENSITY SETTING--

But I only understand as much as the help file explains.  A better explanation may come from the developer.  It is the "cn_config" parameter, which I bolded in the text below.  In Linux, if you type "./teamredminer --help > redhelp.txt, you will have the following help file saved for reference:

    Team Red Miner version 0.3.7                                                                                                               
Usage: teamredminer [OPTIONS]                                                                                                                         
Options:                                                                                                                                             
  -a, --algo=ALGORITHM      Selects the mining algorithm.  Currently available                                                                       
                              algorithms: lyra2z, phi2, cnv8                                                                                         
  -o, --url=URL             Sets the pool URL.  Currently only stratum+tcp                                                                           
                              URLs are supported.                                                                                                     
  -u, --user=USERNAME       Sets the username for pool authorization.                                                                                 
  -p, --pass=PASSWORD       Sets the password for pool authorization.                                                                                 
      --platform=INDEX      Sets the index of the OpenCL platform to use.                                                                             
                              If not specified, platform will be auto-detected                                                                       
                              with a final fallback using index 0.                                                                                   
  -d, --devices=DEVLIST     Sets gpu devices to use from the OpenCL platform.                                                                         
                              DEVLIST should be a comma separated list of device                                                                     
                              indices.  If not specified, all devices on the                                                                         
                              platform will be used.  (example: -d 0,1,4).                                                                           
                              NOTE: if using --bus_reorder, the indices used are                                                                     
                              after reordering. Use --list_devices to show indices.                                                                   
      --rigid               Set the rig identifier that will be sent to the pool.                                                                     
                              This is only used for cryptonight pools.                                                                               
      --init_style=1/2/3    Specified the init style (1 is default):                                                                                 
                              1: One gpu at the time, complete all before mining.                                                                     
                              2: Three gpus at the time, complete all before mining.                                                                 
                              3: All gpus in parallel, start mining immediately.
      --pcie_fmt=FORMAT     Sets print format for pcie bus numbers.  The accepted                                                                     
                              values for FORMAT are either 'hex' or 'dec'.  The                                                                       
                              defaults are decimal for windows and hexadecimal                                                                       
                              for linux.                                                                                                             
      --api_listen=IP:PORT  Enables the api. IP:PORT is optional. If present,                                                                         
                              the IP:PORT combo decides the interface(s) and port                                                                     
                              to listen to. Default is 127.0.0.1:4028. For                                                                           
                              external access, use e.g. 0.0.0.0:4028. It's also                                                                       
                              valid to only specify the port, e.g. 4029.                                                                             
  -l, --log_interval=SEC    Set the time interval in seconds for averaging and                                                                       
                              printing GPU hashrates.  SEC sets the interval                                                                         
                              in seconds, and must be > 0.                                                                                           
      --cn_config=CONFIG    Set the cryptonight configuration for the miner.
                              CONFIG must be in the form [I0][M][I1], where                                                                           
                              [I0] and [I1] are the thread intensity values                                                                           
                              ranging from 1 to 16. [M] is the mode which can                                                                         
                              be either '-' or '+'.  Mode '+' tends to perform                                                                       
                              better for higher core clocks, and '-' tends to                                                                         
                              perform better for lower core clocks.                                                                                   
                              For example: --cn_config=14-14                                                                                         
                              CONFIG can also be a comma seperated list of                                                                           
                              config values where each is applied to each GPU.                                                                       
                              For example: --cn_config=8-8,16+14,15-15,14+14                                                                         
                              Any gpu that does not have a specific config in                                                                         
                              the list will use the first config in the list.
                                                                         
      --pool_broken_rpc     Tells the miner to only allow a single outstanding
                              rpc request on the pool connection.  This is                                                                           
                              a work-around for pools that violate the json                                                                           
                              rpc specification regarding rpc IDs.                                                                                   
      --no_cpu_check        Disables cpu verification of found shares before they                                                                     
                              are submitted to the pool. Note: only CNv8 currently                                                                   
                              supports cpu verification.                                                                                             
      --bus_reorder         Reorders the detected or specified devices after                                                                         
                              their pcie bus id.                                                                                                     
      --list_devices        Lists the available devices for the detected or                                                                           
                              specified platform and exits immediately. Bus                                                                           
                              reordering will be implemented in the order shown.                                                                     
      --help                Display this help message and exit.

I could use a better explanation, really.  And, FWIW, a setting of "16+16" failed to load the kernel on my Vegas, I needed to reboot afterwards.

--scryptr

TIPS:  BTC - 1Fs4uZ6a9ABYBTaHGUfqcwCQmeBRxkKRQT    DASH - XrK81tW31SLsVvZ2WX9VhTjpT6GXJPLdbQ
          ETH - 0x8a42dfAE53612E98daf8614bFA402f3DcD0546Fa    LTC - MKUHfUmRrJUQvELxzajhVaLE5uTPxU2bRK
          SCRYPTR'S NOTEBOOK: https://bitcointalk.org/index.php?topic=5035515.msg46035530#msg46035530  MERIT is appreciated, also.  Thanks!
Bojcha
Hero Member
*****
Offline Offline

Activity: 814
Merit: 500



View Profile
November 09, 2018, 02:06:50 AM
 #219

yea i know. just wonder why there is separate intensity for 2 threads.
scryptr
Legendary
*
Offline Offline

Activity: 1512
Merit: 1002



View Profile WWW
November 09, 2018, 04:22:33 AM
 #220

yea i know. just wonder why there is separate intensity for 2 threads.

MAYBE IT IS "INTENSITY" AND "WORKSIZE"--

And the figures in the config are multipliers for a subroutine in the code.  The miner is simple to configure, fewer choices for the end user.  Just a simple-minded guess on my part.       --scryptr


TIPS:  BTC - 1Fs4uZ6a9ABYBTaHGUfqcwCQmeBRxkKRQT    DASH - XrK81tW31SLsVvZ2WX9VhTjpT6GXJPLdbQ
          ETH - 0x8a42dfAE53612E98daf8614bFA402f3DcD0546Fa    LTC - MKUHfUmRrJUQvELxzajhVaLE5uTPxU2bRK
          SCRYPTR'S NOTEBOOK: https://bitcointalk.org/index.php?topic=5035515.msg46035530#msg46035530  MERIT is appreciated, also.  Thanks!
Pages: « 1 2 3 4 5 6 7 8 9 10 [11] 12 13 »  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!