GPU's are held open by TTMiner even if only CPU mining

[MattF42]

Is it possible to prevent TTMiner from querying, or at least keeping a process running, on GPUs that are not in use by TTMiner for mining?

Thanks

[TrailingStop]

Hi- can you please give me an example that demenstarte what you mean? In general TT only starts a single process. It maybe that from the cuda/opencl system function new processes are started, but that it not under TT control. So a sample with command line would be very helpful. Thanks

[MattF42]

Hi,

The devices I have are:

root@3950x:/home/pi/kyla/TT-Miner-2024.2.1B4# ./TT-Miner -l
17:08:32.504 ********* TT-Miner - Version: 2024.2.1 - Beta 4 (Jun  2 2024 18:34:30)
17:08:32.504 ********* NO DEVFEE!
17:08:32.504 ********* Log system initialized...
17:08:32.504 ********* Internal event system initialized...
17:08:32.504 ********* Worker threads initialized, using 2 threads...
17:08:32.506 ********* Commandline: ./TT-Miner -l
17:08:39.630 ********* CPU/Core information
17:08:39.630       CPU/Core devices:   1
17:08:39.630 * #15                     AuthenticAMD AMD Ryzen 9 3950X 16-Core Processor               CPUs/Cores: 1/32
17:08:39.630 
17:08:39.630 
17:08:39.630 ********* CUDA-GPU information
17:08:39.630 GeForce Driver-Ver:       535.104.5
17:08:39.630 CUDA-Ver:                 12.2
17:08:39.630 NVML-Ver:                 12.535.104-5
17:08:39.630 NVRTC-Ver:                12.4
17:08:39.630 
17:08:39.630       CUDA devices:       15
17:08:39.630 * #00 PCI 27:00.0 nVidia     NVIDIA GeForce RTX 3060 Laptop GPU  6.000 GB / 1.039 GB  SM/Cores: 30/3840  8.6  {6748BEC1-7B2E-F0BC-5FBC-582C573E23D6}
17:08:39.630                              Supported MemClk lock(-oc-mem): 405, 810, 6001, 7001
17:08:39.630 * #01 PCI 28:00.0 nVidia     NVIDIA GeForce RTX 3070 Laptop GPU  8.000 GB / 1.409 GB  SM/Cores: 40/5120  8.6  {C8A64562-8E43-FEC1-2EE1-5F48C6A54232}
17:08:39.630                              Supported MemClk lock(-oc-mem): 405, 810, 6001, 7001
17:08:39.630 * #02 PCI 29:00.0 Zotac      NVIDIA GeForce RTX 2080 SUPER       8.000 GB / 3.165 GB  SM/Cores: 48/3072  7.5  {0F7C41F4-C6D3-2D38-53E8-4F5443F829B6}
17:08:39.630                              Supported MemClk lock(-oc-mem): 405, 810, 5001, 7501, 7751
17:08:39.630 * #03 PCI 2A:00.0 nVidia     NVIDIA GeForce RTX 3070 Laptop GPU  8.000 GB / 1.409 GB  SM/Cores: 40/5120  8.6  {BDB83030-F16F-C105-8E6A-5B76E83CEFB7}
17:08:39.630                              Supported MemClk lock(-oc-mem): 405, 810, 6001, 7001
17:08:39.630 * #04 PCI 2F:00.0 nVidia     NVIDIA GeForce RTX 2070 SUPER       8.000 GB / 1.449 GB  SM/Cores: 40/2560  7.5  {3664DA8A-CE02-0A26-D05A-E197A606C9C3}
17:08:39.630                              Supported MemClk lock(-oc-mem): 405, 810, 5001, 6801, 7001
17:08:39.630 * #05 PCI 30:00.0 nVidia     NVIDIA GeForce RTX 3060 Ti          8.000 GB / 1.680 GB  SM/Cores: 38/4864  8.6  {845877C8-524B-5439-1C67-36C0186762C2}
17:08:39.630                              Supported MemClk lock(-oc-mem): 405, 810, 5001, 6801, 7001
17:08:39.630 * #06 PCI 33:00.0 EVGA       NVIDIA GeForce RTX 2080             8.000 GB / 3.171 GB  SM/Cores: 46/2944  7.5  {5E5D0719-3BA3-B412-4A1C-143E87AD2BD2}
17:08:39.630                              Supported MemClk lock(-oc-mem): 405, 810, 5000, 6800, 7000
17:08:39.630 * #07 PCI 34:00.0 nVidia     NVIDIA GeForce RTX 3060 Laptop GPU  6.000 GB / 1.039 GB  SM/Cores: 30/3840  8.6  {E600431B-0015-C075-2059-6928825250F3}
17:08:39.630                              Supported MemClk lock(-oc-mem): 405, 810, 6001, 7001
17:08:39.630 * #08 PCI 35:00.0 nVidia     NVIDIA GeForce RTX 2070             8.000 GB / 7.687 GB  SM/Cores: 36/2304  7.5  {11140507-C408-1A9D-C615-03519083A3C3}
17:08:39.630                              Supported MemClk lock(-oc-mem): 405, 810, 5001, 5501
17:08:39.630 * #09 PCI 36:00.0 Gigabyte   NVIDIA GeForce RTX 2060 SUPER       8.000 GB / 7.693 GB  SM/Cores: 34/2176  7.5  {9B4EC577-9B4F-C536-31B8-3504E05A2C78}
17:08:39.630                              Supported MemClk lock(-oc-mem): 405, 810, 6801, 6801, 7001
17:08:39.630 * #10 PCI 39:00.0 nVidia     NVIDIA GeForce RTX 3060 Laptop GPU  6.000 GB / 1.037 GB  SM/Cores: 30/3840  8.6  {22061FE7-5B23-B6EA-E671-BAD41654858C}
17:08:39.630                              Supported MemClk lock(-oc-mem): 405, 810, 6001, 7001
17:08:39.630 * #11 PCI 3C:00.0 Palit      NVIDIA GeForce RTX 3080             10.00 GB / 1.731 GB  SM/Cores: 68/8704  8.6  {FA9DE364-DC57-4FA5-455A-3E41C65EC633}
17:08:39.630                              Supported MemClk lock(-oc-mem): 405, 810, 5001, 9251, 9501
17:08:39.630 * #12 PCI 3D:00.0 nVidia     NVIDIA GeForce RTX 3060 Laptop GPU  6.000 GB / 1.039 GB  SM/Cores: 30/3840  8.6  {AFE11069-70DD-316C-A48D-E277D66A9DF6}
17:08:39.630                              Supported MemClk lock(-oc-mem): 405, 810, 6001, 7001
17:08:39.630 * #13 PCI 3E:00.0 nVidia     NVIDIA GeForce RTX 3070 Laptop GPU  8.000 GB / 1.409 GB  SM/Cores: 40/5120  8.6  {7C12F678-F87D-791B-5184-180E53B5AA6F}
17:08:39.630                              Supported MemClk lock(-oc-mem): 405, 810, 6001, 7001
17:08:39.630 * #14 PCI 3F:00.0 nVidia     NVIDIA GeForce RTX 3070 Laptop GPU  8.000 GB / 1.409 GB  SM/Cores: 40/5120  8.6  {BF91C96C-33CF-259B-8A12-D2E1227F600B}
17:08:39.630                              Supported MemClk lock(-oc-mem): 405, 810, 6001, 7001
17:08:39.630 
17:08:39.630 

So I run:

./TT-Miner -d 15 -a FLEX -P ssl://kc1qqftgudagzmawyz4f8r39v97dedtey88qarts5s.3950X:X@fr.vipor.net:5120 -t 31

Then, at any time in the future run nvidia-smi and we get:

+---------------------------------------------------------------------------------------+
| Processes:                                                                            |
|  GPU   GI   CI        PID   Type   Process name                            GPU Memory |
|        ID   ID                                                             Usage      |
|=======================================================================================|
|    0   N/A  N/A      3384      C   /home/pi/rigel-1.9.2/rigel                 4866MiB |
|    0   N/A  N/A      3466      C   ./TT-Miner                                  218MiB |
|    1   N/A  N/A      3384      C   /home/pi/rigel-1.9.2/rigel                 6522MiB |
|    1   N/A  N/A      3466      C   ./TT-Miner                                  274MiB |
|    2   N/A  N/A      2674      C   /home/pi/rigel-1.9.2/rigel                 4730MiB |
|    2   N/A  N/A      3466      C   ./TT-Miner                                  234MiB |
|    3   N/A  N/A      3384      C   /home/pi/rigel-1.9.2/rigel                 6522MiB |
|    3   N/A  N/A      3466      C   ./TT-Miner                                  274MiB |
|    4   N/A  N/A      3384      C   /home/pi/rigel-1.9.2/rigel                 6486MiB |
|    4   N/A  N/A      3466      C   ./TT-Miner                                  202MiB |
|    5   N/A  N/A      3384      C   /home/pi/rigel-1.9.2/rigel                 6244MiB |
|    5   N/A  N/A      3466      C   ./TT-Miner                                  262MiB |
|    6   N/A  N/A      2674      C   /home/pi/rigel-1.9.2/rigel                 4724MiB |
|    6   N/A  N/A      3466      C   ./TT-Miner                                  222MiB |
|    7   N/A  N/A      3384      C   /home/pi/rigel-1.9.2/rigel                 4866MiB |
|    7   N/A  N/A      3466      C   ./TT-Miner                                  218MiB |
|    8   N/A  N/A      2495      C   /home/pi/rigel-1.9.2/rigel                  100MiB |
|    8   N/A  N/A      3466      C   ./TT-Miner                                  190MiB |
|    9   N/A  N/A      2495      C   /home/pi/rigel-1.9.2/rigel                   94MiB |
|    9   N/A  N/A      3466      C   ./TT-Miner                                  178MiB |
|   10   N/A  N/A      3384      C   /home/pi/rigel-1.9.2/rigel                 4860MiB |
|   10   N/A  N/A      3466      C   ./TT-Miner                                  218MiB |
|   11   N/A  N/A      3384      C   /home/pi/rigel-1.9.2/rigel                 8228MiB |
|   11   N/A  N/A      3466      C   ./TT-Miner                                  430MiB |
|   12   N/A  N/A      3384      C   /home/pi/rigel-1.9.2/rigel                 4866MiB |
|   12   N/A  N/A      3466      C   ./TT-Miner                                  218MiB |
|   13   N/A  N/A      3384      C   /home/pi/rigel-1.9.2/rigel                 6522MiB |
|   13   N/A  N/A      3466      C   ./TT-Miner                                  274MiB |
|   14   N/A  N/A      3384      C   /home/pi/rigel-1.9.2/rigel                 6522MiB |
|   14   N/A  N/A      3466      C   ./TT-Miner                                  274MiB |
+---------------------------------------------------------------------------------------+

I think behaviour I'd expect is for TT-Miner not to be running on the GPUs, at least not after an initial scan.

[TrailingStop]

Hi - thanks for these details - I will look into it. guess that are the usage of the device contexts

[MattF42]

Hi - thanks for these details - I will look into it. guess that are the usage of the device contexts

Thanks :). Hardly a priority, but it does slightly impinge on other miners that are runinng, and once the scan is done no reason to keep a handle open on non mining devices. Ta.

[TrailingStop]

No, you are correct. There is no need to load a context for the gpu if it is not used. So - thanks for the information. Will fix it.

[TrailingStop]

Hi, please try beta 5. It comes with a fix for this. Let me know if it works for you now as expected. Thanks

[MattF42]

Perfect, confirmed fixed in B5