Azure Free Credits for Mining Monero/Other CN-Coins. Super-Easy&Super-Profitable

[buonleloi]

It's only reach 600-700H/acc now.
Any one have same issue ? after XMR fork.

[AzureCloudMiningScript]

It's only reach 600-700H/acc now.
Any one have same issue ? after XMR fork.

Have you tried changing to a different region? I.E. if you are using East US, try East US2 instead. Also, make sure that you are really using the "F2"-Type instance (the similar-looking "F2s V2"-instances will give you a lower hashrate),

[buonleloi]

Yes, I've tried many location.
Max 1.3KH now but most of them is less than 800H.
Used to 1.8 - 2KH before fork.

http://prntscr.com/lgomsl

[losi-kc32]

very good.

[AzureCloudMiningScript]

Yes, I've tried many location.
Max 1.3KH now but most of them is less than 800H.
Used to 1.8 - 2KH before fork.
http://prntscr.com/lgomsl

From what i have seen with my miners i suspect that this issue is region-specific, i.e. some regions just don't work so well anymore. Can you confirm this? (unfortunately the regions you are using are not visible from your screenshot)

[buonleloi]

Yes, I can confirm that some regions are bad now ie. West US 2
But hash also drop a lot for other regions. Seem not optimize good for CPU yet.

One tip for you, set huge-page enable to your script that also get more hash.
http://prntscr.com/lguowu

[mubarik]

Literally starting fresh with mining today, and fancied. Basically I get like £120 per month free Azure credits through my company


mining monero btc faucet claim
https://love4youworld.blogspot.com
https://www.youtube.com/channel/UCaAv6fZkpJz2tvS0vtcaNoQ/videos
https://i.imgur.com/Z61V4Gh.png

[AzureCloudMiningScript]

Yes, I can confirm that some regions are bad now ie. West US 2
But hash also drop a lot for other regions. Seem not optimize good for CPU yet.

One tip for you, set huge-page enable to your script that also get more hash.
http://prntscr.com/lguowu

So there was a bug in my autotune-feature for the thread-configuration. Apparently somehow this didn't have a noticeable effect with the pre-fork-algo, but since the fork the resulting hashrate is much worse.
So after fixing the bug the hashrate for 10 instances of F2 is back to around 1.4kH-1.6kH, and it does not seem to be dependent on the region so much anymore.

In order to activate the fix for your miners you can either restart your pool (scale to 0, then scale back to e.g. 10 instances) or you just wait for ca. 3 days (after running for 3 days the miners will fetch the latest version of the script from github).

[buonleloi]

So there was a bug in my autotune-feature for the thread-configuration. Apparently somehow this didn't have a noticeable effect with the pre-fork-algo, but since the fork the resulting hashrate is much worse.
So after fixing the bug the hashrate for 10 instances of F2 is back to around 1.4kH-1.6kH, and it does not seem to be dependent on the region so much anymore.

In order to activate the fix for your miners you can either restart your pool (scale to 0, then scale back to e.g. 10 instances) or you just wait for ca. 3 days (after running for 3 days the miners will fetch the latest version of the script from github).

Your new script seem good but may be need some more tune to get better hash.

Can you try to add this to the script :

"sudo sysctl -w vm.nr_hugepages=128"


[2018-11-12 01:41:41] : Mining coin: monero
[2018-11-12 01:41:41] : Starting 2x thread, affinity: 0.
[2018-11-12 01:41:41] : hwloc: memory pinned
[2018-11-12 01:41:41] : Starting 2x thread, affinity: 1.
[2018-11-12 01:41:41] : MEMORY ALLOC FAILED: mmap failed, check attribute 'use_slow_memory' in 'config.txt'
[2018-11-12 01:41:41] : MEMORY ALLOC FAILED: mmap failed, check attribute 'use_slow_memory' in 'config.txt'
[2018-11-12 01:41:41] : hwloc: memory pinned
[2018-11-12 01:41:41] : MEMORY ALLOC FAILED: mmap failed, check attribute 'use_slow_memory' in 'config.txt'
[2018-11-12 01:41:41] : MEMORY ALLOC FAILED: mmap failed, check attribute 'use_slow_memory' in 'config.txt'
[2018-11-12 01:41:41] : Fast-connecting to pool.supportxmr.com:5555 pool ...
[2018-11-12 01:41:41] : Fast-connecting to pool-ca.supportxmr.com:5555 pool ...

[AzureCloudMiningScript]

Your new script seem good but may be need some more tune to get better hash.
Can you try to add this to the script :
"sudo sysctl -w vm.nr_hugepages=128"

Yeah, i know about this issue. Actually, when i originally setup the script i did a lot of benchmarking to find out the optimal settings for the VMs in the azure-cloud. This hugepages-setting did not make any noticeable difference, so i did not bother including it in the script. I think this setting is mostly useful if you are mining on a real machine (maybe then you get that +20% hashrate that is mentioned on some mining-guides). Since with azure we are always inside a VM the effect is not there.
But you are right, the messages in the log from xmr-stak do not look good... since the setting also did not have a negative effect, i will include it in the script.
Thanks for your suggestion!

[DByte]

is there any script for google cloud?

[BillieCrypt]

Hashrate 1600 H/s according to whattomine.com calculator now gives 28 dollars a month without electricity during Monero mining. If a monthly subscription to the Azure service costs less, then this is a net benefit. I’ll probably try your way of mining.

[AzureCloudMiningScript]

is there any script for google cloud?

here's a very rough guide how to set it up with the google cloud:

Create the instance template:
Settings:
Machine-type: 2vCPUs, 1.8Gb RAM  (i think 2vCPUs per Instance gives the best performance, but i have not yet tested it thoroughly)
Click on "Management, security, disks, networking, sole tenancy"   to open additional options
Preemptibility : On  (for less cost)

startup-script: -> insert here the generated script from my guide at https://azurecloudminingscript.github.io/Turn_your_Azure_Free_Credits_into_Cryptocurrency.html

Leave the other options at the default.


Create Instance group
Settings:
instance.template: select the previously generated template
Autoscaling: off
Number of instances: enter the number of desired instances

Conclusion
For the "number of instances" i chose 10, but apparently there's some quota relating to IP-addresses, so it would only create 8 instances for me.
* Choose "Multi-Zone" when creating the instance-group -> this should make it easier for google to find free resources for your VMs
* From my testing ivy-bridge and broadwell get the best hashrate. I recommend using the region asia-east1, because that has the ivy-bridge-cpu-type as the default.
* I heard that google will ban you very fast if you are using a free account. For my personal testing-account, i have upgraded right away to the paid-version (this won't make your free credits expire, so it's no problem). After some weeks of mining i have not been banned yet.

For 8 instances with 2 cores (i.e. 16 cores total) i get around 700 H/s.

[buonleloi]

Actually it can not reach 1600H for almost account.
May be need some change from the dev xmr-stak.

[AzureCloudMiningScript]

Actually it can not reach 1600H for almost account.
May be need some change from the dev xmr-stak.

Yes, the new algo after the fork apparently is a bit more difficult to calculate. From what i have read also the GPU-Miners experienced some drop in hashrate (and also the hashrate of the whole network went down).
I will update the information in the first post in this thread accordingly.
 

[buonleloi]

One more important thing that xmr-stak was recognized virus by MS when xmrig didn't
It could be a reason that MS would block the account after some days running.

[buonleloi]

CPU v3 get better than v4.

http://prntscr.com/lk2gtk

http://prntscr.com/lk2hzh

[AzureCloudMiningScript]

CPU v3 get better than v4.

http://prntscr.com/lk2gtk

http://prntscr.com/lk2hzh

Yeah, the F-instances (which are E5-2673 v3) indeed work better than the FsV2-instances, at least for monero.

(That's not true for all algos, btw. Nimiq-mining for example has better performance with the FsV2-type).

[buonleloi]

Yeah, the F-instances (which are E5-2673 v3) indeed work better than the FsV2-instances, at least for monero.

(That's not true for all algos, btw. Nimiq-mining for example has better performance with the FsV2-type).

Some location have v4 CPU even with F2 Series.

[mk111]

Please add this to your scripts.

https://bitcointalk.org/index.php?topic=5086106.0

Conceal - Cryptonight-Fast