Pages:
Author

Topic: [ANN] TeamRedMiner - Optimized Win/Linux AMD GPU Miner for lyra2z and phi2 - page 31. (Read 85798 times)

Lno
newbie
Activity: 9
Merit: 0
If the pool fell off? how to prescribe that he cling to the spare?

Man, I understand English isn't your first language and this is most probably a google translate post, but that's just the best hippie statement in a long time, lmao!

For your question: we will add failover pool support shortly, promise!
Thank. Sorry for the google translator Grin Grin Grin
member
Activity: 658
Merit: 86
If the pool fell off? how to prescribe that he cling to the spare?

Man, I understand English isn't your first language and this is most probably a google translate post, but that's just the best hippie statement in a long time, lmao!

For your question: we will add failover pool support shortly, promise!
Lno
newbie
Activity: 9
Merit: 0
If the pool fell off? how to prescribe that he cling to the spare?
legendary
Activity: 1797
Merit: 1028

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

Ha, sorry about that. You'd need a Vega FE to pull off a 16+16 config Smiley. It would translate into a full 8GB allocation on your Vega. The weird part is that the driver actually says "sure, let's go" and tries to allocate the buffers instead of throwing an error in our faces so we can exit with some dignity.

THANK YOU--

The program is good, it unlocked my Linux-bound Vegas.  Please continue the progress!       --scryptr
member
Activity: 658
Merit: 86

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

Ha, sorry about that. You'd need a Vega FE to pull off a 16+16 config Smiley. It would translate into a full 8GB allocation on your Vega. The weird part is that the driver actually says "sure, let's go" and tries to allocate the buffers instead of throwing an error in our faces so we can exit with some dignity.
member
Activity: 658
Merit: 86
yea i know. just wonder why there is separate intensity for 2 threads.

Hi! In our case, the reason for letting the user specify the per-thread intensity is that the behavior on e.g. a Vega 64 for 15+15 vs 16+14 is not the same, although the combined intensity would be the same. It depends on clocks, brand, memory, silicon lottery, rig optimization style.
legendary
Activity: 1797
Merit: 1028
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

hero member
Activity: 848
Merit: 500
yea i know. just wonder why there is separate intensity for 2 threads.
legendary
Activity: 1797
Merit: 1028
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
hero member
Activity: 848
Merit: 500
Can you explain what exactly is 14+16 or 14-14?
legendary
Activity: 1797
Merit: 1028
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

newbie
Activity: 3
Merit: 0
http://I am very satisfied
I get with vega 64 1950h srb 1.6.8
 TeamRedMiner 2090h
and vega 56 1850h srb
TeamRedMiner 2060h
jr. member
Activity: 98
Merit: 1
yes, thanks! lyra2z, then phi2 and now excelent cnv8 miner. you gave hope back for my team red cards.
member
Activity: 588
Merit: 61
Thanks dev. I'll give it a try. TeamRedMiner is cool ... Grin
member
Activity: 176
Merit: 76
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.
newbie
Activity: 24
Merit: 0
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!
member
Activity: 176
Merit: 76
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.
jr. member
Activity: 195
Merit: 4
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.
member
Activity: 658
Merit: 86
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!
jr. member
Activity: 195
Merit: 4
What which drivers are we supposed to be using with Windows? amdgpu-pro drivers???

Is that 18.5.1? 18.6? 18.10??
Pages:
Jump to: