Episode 67 - Technical Computing with Windows Azure and Wenming Ye

Play Episode 67 - Technical Computing with Windows Azure and Wenming Ye

The Discussion

  • User profile image

    Is there any special price for using HPC Scheduler SDK on Azure (on-line version)?
    On the following web page:
    there is only price for the compute instance. There is nothing about HPC computing.

    From the presentation I got an impression that it is necessary to copy separate executable file on each compute node separately.
    Is there anything like UNC-path on azure? Is there anything like current directory on azure mpi cluster?

  • User profile image

    There is no special pricing for the HPC Scheduler, other than the components it uses:

    CPU hours - head node role, compute role, and frontend role. You will be billed for the number of cpu hours those machine use, which depends on the type of machines and the number of instances you defined (the default is 5xSmall node) during the deployment.

    Storage - to hold your deployed HPC applications, so you will be billed for the storage (GB/month), and for storage transaction (that can reach a couple of hundreds of thousands transactions per month, which is a couple of cents).

    SQL Azure - the cluster uses a server with one database (other than the master), which is either 1 or 5 gb (depends on the technique of deployment). You will pay for those databases as you pay for other SQL Azure databases.

    Of course if your client is outside the cloud, you will also be billed for download bandwidth of getting result from the cloud (upload of data is free in azure)

  • User profile image

    Thank you for the information about the pricing.

    According to my experience in the area of hpc computing there is a lot of linux/unix software, which can be used also on the Windows platform. The only problem is the unix build system and basic scripting functionality (e.g. bash).
    Adding something like MSYS and basic unix tools like in SUA but for Win32 to Widnows HPC Server and/or Azure would be probably a good idea. In this way utilization and development of open source software on Windows would be much faster.

    There is SUA however, the support for SUA is very bad and this subsystem is deprecated in Windows 8. So it looks like it is better to stay away from that.

Conversation locked

This conversation has been locked by the site admins. No new comments can be made.