Gateless Gate Sharp 1.3.8: 30Mh/s (Ethash) on RX 480!

[zawawa]

Gateless Gate Sharp 1.2.3 alpha
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.2.3-alpha

* Reorganized CPU threads for efficiency.
* Added charts for relevant statistics.
* Added features for managing user settings.
* Made user interface more responsive.

The new version should be pretty useful. Enjoy!

Start to give BSOD Thread_stuck_in_device_driver. Lowering overclock didn't helped.
Several seconds after pressing "Start" and BSOD...
1.2.2 works normal... Rolling back...

It could well be modded BIOS'es... Especially with NeoScrypt.

[UnclWish]

Gateless Gate Sharp 1.2.3 alpha
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.2.3-alpha

* Reorganized CPU threads for efficiency.
* Added charts for relevant statistics.
* Added features for managing user settings.
* Made user interface more responsive.

The new version should be pretty useful. Enjoy!

Start to give BSOD Thread_stuck_in_device_driver. Lowering overclock didn't helped.
Several seconds after pressing "Start" and BSOD...
1.2.2 works normal... Rolling back...

It could well be modded BIOS'es... Especially with NeoScrypt.

No, it's cryptonight. All previous versions works with the settings taken from previous version.
Untill 1.2.2 works fine. 1.2.3 start to give BSOD in start. I tried to lower overclock settings, but it didn't helped.
Returned to 1.2.2 and with these settings GGS work again...
In morning I haven't much time. After my work I try to rise voltage on 1st GPU, maybe statistic charts increase 1st GPU load...

Another one question: how you make binary kernels? I think that these kernels must be built for each card individually to achieve best results, because of different systems/drivers/memory timings/etc. That's why on one of my cards maximum speed can be reached only after several launches. But without binary kernel file, speed allways achieves maximum, but slow starting.
Maybe better make building binary kernels at 1st start on client machine? Like it was in Gateless gate?

[zawawa]

Untill 1.2.2 works fine. 1.2.3 start to give BSOD in start.

I see. GSS'es internals changed quite a bit with v1.2.3 and they are much more efficient than before.
Ironically, that makes GGS less tolerant of overclocking and memory timing mods.

I think that these kernels must be built for each card individually to achieve best results, because of different systems/drivers/memory timings/etc. That's why on one of my cards maximum speed can be reached only after several launches. But without binary kernel file, speed allways achieves maximum, but slow starting.
Maybe better make building binary kernels at 1st start on client machine? Like it was in Gateless gate?

Nah, it really doesn't work that way. It is generally preferable to ship the miner with binaries because you would never be sure that the user's driver would always produce better binaries.

[UnclWish]

I think that these kernels must be built for each card individually to achieve best results, because of different systems/drivers/memory timings/etc. That's why on one of my cards maximum speed can be reached only after several launches. But without binary kernel file, speed allways achieves maximum, but slow starting.
Maybe better make building binary kernels at 1st start on client machine? Like it was in Gateless gate?

Nah, it really doesn't work that way. It is generally preferable to ship the miner with binaries because you would never be sure that the user's driver would always produce better binaries.

Maybe you can add an advanced option to rebuild binaries? It's hard?

[Jahare]

1.2.3 seems pretty stable so far, really like the graph and choices.  Do not see any performance hit.  Nice job!

[Branko]

How is lyra2v2 performance compared to mkxminer?

[zawawa]

I think that these kernels must be built for each card individually to achieve best results, because of different systems/drivers/memory timings/etc. That's why on one of my cards maximum speed can be reached only after several launches. But without binary kernel file, speed allways achieves maximum, but slow starting.
Maybe better make building binary kernels at 1st start on client machine? Like it was in Gateless gate?

Nah, it really doesn't work that way. It is generally preferable to ship the miner with binaries because you would never be sure that the user's driver would always produce better binaries.

Maybe you can add an advanced option to rebuild binaries? It's hard?

It's not hard at all, but I would rather like things to be predictable, you know.
AMD drivers are already so unpredictable...

[UnclWish]

I think that these kernels must be built for each card individually to achieve best results, because of different systems/drivers/memory timings/etc. That's why on one of my cards maximum speed can be reached only after several launches. But without binary kernel file, speed allways achieves maximum, but slow starting.
Maybe better make building binary kernels at 1st start on client machine? Like it was in Gateless gate?

Nah, it really doesn't work that way. It is generally preferable to ship the miner with binaries because you would never be sure that the user's driver would always produce better binaries.

Maybe you can add an advanced option to rebuild binaries? It's hard?

It's not hard at all, but I would rather like things to be predictable, you know.
AMD drivers are already so unpredictable...

Agreed, but I would like to try it myself... Especially after changing timings...
At this moment as I undersand right, if timings too different from timings of card from wich binary builded, speed may be not max... Maybe I wrong...

[zawawa]

Gateless Gate Sharp 1.2.4 alpha
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.2.4-alpha

* Numerous bug fixes around stratum-related codes.

GGS should be much more robust against network/server failures.
It's getting there!

[zawawa]

Agreed, but I would like to try it myself... Especially after changing timings...
At this moment as I undersand right, if timings too different from timings of card from wich binary builded, speed may be not max... Maybe I wrong...

Sure. I will include it in v1.2.5.

[UnclWish]

Agreed, but I would like to try it myself... Especially after changing timings...
At this moment as I undersand right, if timings too different from timings of card from wich binary builded, speed may be not max... Maybe I wrong...

Sure. I will include it in v1.2.5.

Thanks! I'll very greatful for this!

And finally I find what couses BSOD... It's enabling overclocking/underclocking on my Pitcairn 270X 4Gb. Even if GPU disabled in dashboard, but in settings option "Overclocking/underclocking" is enabled, starting mining leads to BSOD. If disable it, all works fine.
And it not due to memory timings or other overclocking. I make overclock and undervoltage via other tool and start GGS with disabled OC option on this GPU, and all works fine. Option on RX 580 working normal...

[Vovchik]

zawawa.
Hi.Please order on Nicehash, you could choose the location manually.Thank you.Sorry for my English.

[zawawa]

Agreed, but I would like to try it myself... Especially after changing timings...
At this moment as I undersand right, if timings too different from timings of card from wich binary builded, speed may be not max... Maybe I wrong...

Sure. I will include it in v1.2.5.

Thanks! I'll very greatful for this!

And finally I find what couses BSOD... It's enabling overclocking/underclocking on my Pitcairn 270X 4Gb. Even if GPU disabled in dashboard, but in settings option "Overclocking/underclocking" is enabled, starting mining leads to BSOD. If disable it, all works fine.
And it not due to memory timings or other overclocking. I make overclock and undervoltage via other tool and start GGS with disabled OC option on this GPU, and all works fine. Option on RX 580 working normal...

What are GGS's default values for core/memory clocks and core voltage for 270X?

[zawawa]

zawawa.
Hi.Please order on Nicehash, you could choose the location manually.Thank you.Sorry for my English.

This isn't really necessary, but if you insist...

[treanski]

@zazawa something is wrong with 1.2.3 & 1.2.4 i tried it now few time over the day, after some time miner stops submiting shares but still hashin at full speed
see picture, due the dips miner was running @ full speed



i roll back to 1.21, was the most stable for me

[wtfonly16]

this any good ??

[zawawa]

@zazawa something is wrong with 1.2.3 & 1.2.4 i tried it now few time over the day, after some time miner stops submiting shares but still hashin at full speed
see picture, due the dips miner was running @ full speed



i roll back to 1.21, was the most stable for me

This looks like a pool problem. I will implement a workaround.

[treanski]

i was mining on nicehash cryptonight

[zawawa]

i was mining on nicehash cryptonight

Yeah, I thought so. Something is wrong with the pool.

[UnclWish]

Agreed, but I would like to try it myself... Especially after changing timings...
At this moment as I undersand right, if timings too different from timings of card from wich binary builded, speed may be not max... Maybe I wrong...

Sure. I will include it in v1.2.5.

Thanks! I'll very greatful for this!

And finally I find what couses BSOD... It's enabling overclocking/underclocking on my Pitcairn 270X 4Gb. Even if GPU disabled in dashboard, but in settings option "Overclocking/underclocking" is enabled, starting mining leads to BSOD. If disable it, all works fine.
And it not due to memory timings or other overclocking. I make overclock and undervoltage via other tool and start GGS with disabled OC option on this GPU, and all works fine. Option on RX 580 working normal...

What are GGS's default values for core/memory clocks and core voltage for 270X?

Default GGS values is the same as in vbios - 1070/1400 and 1.2V

And it's need a binary kernel for Pitcairn...

Up to version 1.2.2 on Pitcairn after one-two Stop-Start I recieved 510-515 h/s, from version 1.2.3 max 497...

1.2.3 and 1.2.4 versions uses too much CPU power. Maybe because of charts... On my 8 cores FX8320 CPU load from 14 to 18% during mining and about 30% at start. It's too much!

And it was bad idea to save config on system drive. GGS too much writes to drive where config is. GGS now to much writes to my SSD...