Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Abel Avram on Nov 26, 2010
Amazon has announced the availability of Cluster GPU instances for high performance applications starting with an instance of 2 NVidia Tesla GPUs and going up to a cluster of 128 or more instances, appealing to financial analysis, imaging, biology, simulation, and other domains.
Amazon is offering a Cluster GPU instance for those who need a HPC platform but cannot afford one or do not want to support the initial cost of setting up one. The Cluster GPU instance belongs to the HPC group of instances, offering the equivalent of 33.5 EC2 Compute Units based on a pair of Intel Xeon X5570 quad-core Nehalem processors. A Compute Unit is the computing power offered by a 1 GHz Opteron or Xeon processor manufactured in 2007. Besides that, the GPU instance comes with a pair of NVIDIA Tesla Fermi M2050 GPUs, each unit offering: 515 double-precision Gflops or 1 single-precision Tflops, 3 GB DDR5 memory accessed on a 384-bit bus sustaining a bandwidth of 148 GB/sec. The instance also includes 22 GB of internal RAM and 1690 GB of disk storage. The user has the ability to organize 128 or more instances in clusters, communicating between them on 10 Gbps network links.
Currently only Linux is supported on a Cluster GPU instance, allowing developers to program in FORTRAN, C, C++, Java, Python, or Ruby against the GPU’s CUDA Driver API or CUDA C Runtime. Users can also make use of Amazon Elastic MapReduce web service and Public Data Sets when dealing with vast amounts of data which is common for HPC applications. The Cluster GPU instance is currently available only in US-N.Virginia region at $2.10/hour.
There are already other vendors offering GPU in the cloud such as Peer1, Nimbix, Penguin Computing or Hoopoe. They are providing solutions based either on NVidia Tesla or AMD FireStream technologies. The number of such vendors is supposed to rise in the following years because GPUs have become attractive for computational-heavy applications due to their high processing power and after including more and more general-purpose computation functionality taken from traditional CPUs.
RDBMS to NoSQL: Managing the Transition
Why NoSQL? A Primer on the Rise of NoSQL
App Server Evolution: REST, Cloud, and DevOps Support in Resin 4
Want to know how software releases can be stress-free and happen with one click? Try Go free!
Improving Software Delivery Cycles: Pre-requisites and Inhibitors
Go: Agile Release Management Solutions. Go enables predictable, defect-free and timely software releases.
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
No comments
Watch Thread Reply