HPC Cloud Anatomy 101
February 5, 2015
Grazed from SysCon Media. Author: Leo Reiter.
When it comes to cloud computing, there is no "one size fits all" platform for getting work done. High Performance Computing (HPC) workloads are not web applications. Thankfully, there are clouds specifically designed for running HPC workloads rather than web applications. An HPC cloud is very different to a commodity web services cloud. Before we discuss how an HPC Cloud is architected, we need to examine HPC workloads themselves to really understand how they differ from other applications:
- HPC jobs process data – most often enormous amounts of data (Big Data) and return results. In other types of clouds, "instances" (virtual servers) run when launched and listen for requests. HPC workloads typically run in "batch" mode, where the data and the parameters are queued together with the application for execution. Other types of cloud workloads offer services that often require further interaction to do any processing…
- HPC jobs "shut down" as soon as they finish, again due to their batch nature. In a pay-per-use model, end-users need not need worry about managing the underlying infrastructure in order to save money, and are billed only for the processing cycles their jobs consume…
Read more from the source @ https://cloudcomputing.sys-con.com/node/3293658