2012
DOI: 10.1007/s00779-012-0605-3
|View full text |Cite
|
Sign up to set email alerts
|

Evaluation of messaging middleware for high-performance cloud computing

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
2
0

Year Published

2013
2013
2017
2017

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 7 publications
(3 citation statements)
references
References 20 publications
0
2
0
Order By: Relevance
“…In this paper, we consider Amazon EC2 cloud and use CGI heterogeneous instances, which consist of a dual-socket CPU host and two GPUs, and connected over 10 Gbps Ethernet with latency 60 μs [21]. The CPU host has two Intel Nehalem x5570 multicore processors coupled via QPI links with speed of 25.6 GB/s.…”
Section: Hardware Architecture Modelmentioning
confidence: 99%
“…In this paper, we consider Amazon EC2 cloud and use CGI heterogeneous instances, which consist of a dual-socket CPU host and two GPUs, and connected over 10 Gbps Ethernet with latency 60 μs [21]. The CPU host has two Intel Nehalem x5570 multicore processors coupled via QPI links with speed of 25.6 GB/s.…”
Section: Hardware Architecture Modelmentioning
confidence: 99%
“…Another paper entitled ''Evaluation of Messaging Middleware for High Performance Cloud Computing'' by Doallo et al [7] presents an evaluation of high-performance computing message-passing middleware on a cloud computing infrastructure, Amazon EC2 cluster compute instances, equipped with 10 gigabit Ethernet. The analysis of the experimental results, confronted with a similar testbed, has shown the significant impact that virtualized environments still have on communications performance, which demands more efficient communication middleware support to get over current cloud network limitations.…”
Section: Other Issues In Ubiquitous Computingmentioning
confidence: 99%
“…In other words, the simple addition of instances and the use of load balancers have no effect in these applications since they are not able to detect and use these resources [11]. Technically, over recent years most parallel applications have been developed using the Message Passing Interface (MPI) 1.x, which does not have any support for changing the number of processes during the execution [12]. While this changed with MPI version 2.0, this feature is not yet supported by many of the available MPI implementations [9].…”
Section: Introductionmentioning
confidence: 99%