Topic: Azure Free Credits for Mining Monero or CN-Heavy:Super Easy and Super Profitable - page 7. (Read 24184 times)

FYI: i have updated the previous post on how to work with AWS.

I have not personally used my script with AWS, but one nice person has actually got it to work. He gave me these instructions:
Apparently there's some subtle difference in the way AWS and azure call the startup-scripts. So for now my script-generator won't work with AWS. However, you can use the template linked above to manually create your own script.

Note that i don't have a AWS-account (yet), so i can't really help you if you run into problems. But you can write a post here anyway, i'll do my best...

edit: added more detailed instructions and added information on how to use the startup-script

Hello I saw your azure cloud mining bash script. Can you provide the xmr stak bash script for aws cloud mining too ?

I don't know the details, but i can tell you that at least for mining Nimiq in Azure the Fv2-type (skylake) will give a lot more performance than the F-type (Haswell). On the other hand, mining Monero works better on the F-type -> That's why i think i think it's less a question of the cache, it probably has to do with the instruction set.

I can't find this info anywhere, can someone clue me in as to what type of hardware mines Nimiq the best?  I know its obviously a CPU, but is cache a factor?  Does having a processor with sha-512 increase hashrate?

Hi impynick,

apparently azure has changed the default-quotas for new accounts.
Anyway, the number of batch-accounts and pools is not important, as long as the total number of instances adds up to your desired value (and you'll thus get the desired hashrate).
Basically, if azure does not let you increase the number of instances in a pool, just create an additional batch-account in another region and create the additional pool there (if i understand correctly you have already started doing this).
Typically maintaining everything is easier if you have fewer pools with many nodes instead of having lots of pools with fewer nodes, but the hashrate will be the same.

So to use up the starting credits you could use the following configuration:
Batch account "batch1" with pool "pool1" in region "East US" with 5 Nodes.
Batch account "batch2" with pool "pool2" in region "East US2" with 5 Nodes
Batch account "batch3" with pool "pool3" in region "West US2" with 5 Nodes.
This should give you a total of 30 cores, which should consume the 200$ within one month.

(you could also try creating an additional batch-account in North Central US, but i think there's also a limit of 3 batch-accounts. Anyway, even though this would increase your hashrate, you'll consume your credits faster - in the end the profit will be the same)

I emailed you as well.

I’m having an issue getting the hash rate I want.

Am I suppose to have more than 1 batch? I currently have 2 batches on us west and us west central.

I have 5 pool IDs. Each one using only 1 node as I can only use a max of 10 cores. 1 node = 2 cores

What am I messing up??

In my experience F2 will give the best hashrate per core (this is due to the way cryptonight works with the CPU-Cache - read my initial post to find out more about the autotune-feature of the script). In your case i would suggest setting up two pools (in different regions, e.g. "East" and "East 2") and using 10 instances of F2 each. Since you are just using the initial credit of 200$ you don't really care about the monthly cost, you just want to use it up within one month.

yup, 200$ is only for 1st month, than you will need to pay, if you want to continue.

Don't worry. Just start following the guide, after that the words will make sense to you. Then  you can create your second pool.

I believe the 200$ starting credit is valid only for the first month. Maybe you could double-check the conditions. Anyway, the amount of generated cryptocurrency will be the same, whether you spend 200$ in a single month or over a longer time-period.

Yes, it's still working. At the current exchange-rate you'll get around 50$ worth of cryptocurrency for 200$ in azure credits. You'll have to create two batch-pools in different regions in order to consume your 200$ free credits within one month.

The first version of the mining-script-generator for NIM is ready: check out https://azurecloudminingscript.github.io/Turn_your_Azure_Free_Credits_into_NIMIQ.html

Thanks for info. I am currently trying it out and will make a prototype for a azure-script-generator for NIM. Stay tuned!

How about Verus?

https://bitcointalksearch.org/topic/ann-verus-vrsc-zk-snark-privacy-cpu-mining-5050-powpos-fair-launch-4070404

System requirements:
Mining and staking wallets are available for Windows, Linux, and Mac. Currently, you will require an Intel or AMD processor with AES and AVX instructions. Most Intel or AMD CPUs made within the past 5 or 6 years support these instructions. You can check yours specifically by running this free utility: https://www.cpuid.com/ or using the "lscpu" command on Linux.

CPU Mineable
Verus uses VerusHash, the fastest cryptographic hash algorithm in the world on x64 CPUs, equalizing GPUs and offering a credible ASIC solution.

Yeah, i've been thinking of testing other coins besides XMR in order to find the most profitable thing.
Do you have personal experience mining NIM, especially with azure? What Hashrate can i expect on a server-class CPU? Which mining-software is your favorite?

You're welcome 

Actually we all have to thank Microsoft for being so generous with the free credits...

Thanks AzureCloudMiningScript.
I am still mining strong on my Azure account

Hi everybody,

FYI: I have updated the used xmr-stak-code to the latest version. I will probably update the next time in october in preparation for the next Monero network update.

Hi everybody,
FYI: after my azure-account was deactivated before the end of the month, i have found out that the batch-service in the "West US" and the "West US 2"-regions do in fact have different pricing...
Conclusion: If you are experimenting with the region-settings, make sure that you are checking the pricing of the exact region you are testing first.