Device level communication libraries for high‐performance computing in Java

Abstract

SUMMARYSince its release, the Java programming language has attracted considerable attention from the highperformance computing (HPC) community because of its portability, high programming productivity, and built-in multithreading and networking support. As a consequence, several initiatives have been taken to develop a high-performance Java message-passing library to program distributed memory architectures, such as clusters. The performance of Java message-passing applications relies heavily on the communications performance. Thus, the design and implementation of low-level communication devices that support messagepassing libraries is an important research issue in Java for HPC. MPJ Express is our Java message-passing implementation for developing high-performance parallel Java applications. Its public release currently contains three communication devices: the first one is built using the Java New Input/Output (NIO) package for the TCP/IP; the second one is specifically designed for the Myrinet Express library on Myrinet; and the third one supports thread-based shared memory communications. Although these devices have been successfully deployed in many production environments, previous performance evaluations of MPJ Express suggest that the buffering layer, tightly coupled with these devices, incurs a certain degree of copying overhead, which represents one of the main performance penalties. This paper presents a more efficient Java message-passing communications device, based on Java Input/Output sockets, that avoids this buffering overhead. Moreover, this device implements several strategies, both in the communication protocol and in the HPC hardware support, which optimizes Java message-passing communications. In order to evaluate its benefits, this paper analyzes the performance of this device comparatively with other Java and native message-passing libraries on various high-speed networks, such as Gigabit Ethernet, Scalable Coherent Interface, Myrinet, and InfiniBand, as well as on a shared memory multicore scenario. The reported communication overhead reduction encourages the upcoming incorporation of this device in MPJ Express (http://mpj-express.org). Copyright

Study and Design of Distributed Badminton Agility Training and Test System

“…Lower computers establish a client and transmit comprehensive response time data from each round to the upper computer in real time. When the user opens a WiFi hotspot via their mobile phone, the upper computer connects to the hotspot and uses JAVA Socket [25,26] technology to create multiple threads and implement TCP/IP based on the wireless connectivity and communication. This establishes wireless connectivity and communication within the LAN for the entire system.…”

Low‐latency Java communication devices on RDMA‐enabled networks

“…Although the current MPI standard declaration is limited to C and Fortran languages, there have been a number of standardization efforts made towards introducing an MPIlike Java binding. However, mpiJava can incur a noticeable JNI overhead [43] and presents some inherent portability and interoperability issues derived from the amount of native code that is involved in a wrapper-based implementation (note that all the methods of the MPJ API have to be wrapped). Currently, the most relevant implementations of this API are Open MPI Java, MPJ Express, and FastMPJ, next presented.…”

“…Additionally, the hybrid device (hybdev) allows to use simultaneously niodev and smpdev for inter-node and intra-node communications, respectively. However, the overall design of MPJ Express relies on an internal buffering layer that significantly limits performance and scalability [43]. However, the overall design of MPJ Express relies on an internal buffering layer that significantly limits performance and scalability [43].…”

“…mpiJava [41] consists of a collection of wrapper classes that use JNI to interact with an underlying native MPI library. However, mpiJava can incur a noticeable JNI overhead [43] and presents some inherent portability and interoperability issues derived from the amount of native code that is involved in a wrapper-based implementation (note that all the methods of the MPJ API have to be wrapped). More recently, Open MPI [44] has revamped this project and included Java support in the developer code trunk.…”

“…Furthermore, the recently released native device [48] enables MPJ Express to exploit the latest features of native MPI libraries through JNI. However, the overall design of MPJ Express relies on an internal buffering layer that significantly limits performance and scalability [43].…”