Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 118. (Read 703547 times)

Hi patrike
looks like my solution not works always(( sometimes yes, sometimes no. I have increased delay time, but this caused other problem, service stuck in "pre-start" state after rebooting.
Looks like awesome.service code must better check GPU initialization before delegate control to AwesomeMiner main program.
Hope you solve this quickly. Till this only manual restarting helps.

Regards.

Thanks for all detailed feedback and good that you found a workaround. I will look into this scenario to find a better way for Remote Agent to handle it.

upd: Solved!

simple add a pause before service start. For my 8 GPU rig i needed extra 50 sec. delay to properly initialize all GPUs (if you guys have rigs with more cards or general slow system, simple increase delay)

I have added one string in [Service] section in awesome.service file:

[Service]
ExecStartPre=/bin/sleep 50
ExecStart=/awesomeminer-remoteagent/AwesomeMiner.RemoteAgent.Linux

Hi Patrike, I have not written to you for a long time, you are doing a great job as always, I remind you of an old request from me and I propose a new one.

Old request:

Know in statistics the times you make profit change in 24 hours and for each moment. To determine if that percentage of mining of a coin has done it in 1 change or in 30. It would help me to make better decisions

The other request is an improvement on something existing. I mean temperature control, which is going very well but I explain.

I use both methods, both the general by TDP with its two options and also the core reduction. My scheme is as follows

TDP 1 limitation: 72 degrees, you under the TDP

TDP 2 limitation: 74 degrees, even more under the TDP

Temperature limitation in each OC or core, I have it at 76 degrees

What is the problem ?, Well, it works well, but is constantly jumping temperature. I have a card that according to the Algorithm gets very hot and is always dancing the temperature of 72 to 76 degrees. Because what happens that when it falls to 71 or 72 the limitations are removed and reheated, when it is heated, the limitations are activated and the temperature is lowered, but then the limitations are removed and again heated. I think that so much temperature change, TDP and core can be even bad.

The idea or solution I see simple. If a card activates a temperature limit for example TDP 1, this limit remains active until it changes algorithm or currency. This way we avoid getting the cards receiving a constant change of TDP and CORE all the time. It is logical that if it reaches TDP 1 and 2 and the temperature drops, if we remove the limitation it warms up again. That's why I think it's a better idea to keep the limitations until you change your currency. That way the temperature would be more stable, and I wouldn't be hitting jumps all the time between 72 and 76 as is my case, I don't want it to reach 76 every time.

I hope it is understood and that you see it well as an idea, the implementation is very easy, basically because almost everything is done, just keep limitations until currency exchange, with which the temperature will not be jumping, we are not changing TDP and CORE several times per minute to the card