What is pros and cons of CycleCloud vs Azure Batch when it comes to HPC?

I will claim some personal responsibility for the slide - I made it 🙂 (that includes any inaccuracies!). Originally made for an internal Microsoft training, but also now used in slide decks for external presentations as Andy said.

To add a bit more detail on a cost example - while both products are free to use - CycleCloud uses an Azure VM to host it's web/db service, which is an additional cost to the HPC clusters you make (e.g. ~$150/month if left on all the time). You can choose a small VM, and you can turn it off when you're not using it (much like the HPC clusters themselves!), or hugely discount it over 1 or 3 years.

Cost is a big topic. We'll write & share more in future! You can always play with the Azure Cost Calculator - and I made a sample HPC cluster example for 10 nodes (with our latest HBv4 machines - i.e. 1760 cores, 6 TiB RAM, 36 TB disk) - for 100 hours = ~$7238. BUT: it's not just about the cores/RAM/disk - it's about how fast you can get your simulation to run (time is also money) with the right configuration - and also about the value this creates for your business or scenario.  This might be the fastest/cheapest cluster for a large CFD job, but not for a genomics pipeline.  This was also done assuming pay-as-you-go pricing without any reservations, spot (90% cheaper!!) or other discounts. https://azure.com/e/6e1736448e7f43c5866d5c688252149b