Combining data sharing with the master–worker paradigm in the common component architecture

Abstract

Software component technologies are being accepted as an adequate solution for handling the complexity of applications. However, existing software component models tend to be specialized to some types of resource architectures (e.g. in-process, distributed environments, etc.) and/or do not provide a very high level of abstraction. This paper focuses on handling data sharing on operation invocations between components as a solution allowing applications to be efficiently executed on all kinds of resources. In particular, the data sharing pattern appears in master-worker applications, when workers need to access only a part of a large piece of data, either in read or write mode. This approach is applied to the Common Component Architecture model. Its benefits are discussed using an image rendering application.

Towards dynamic adaptability support for Master-Worker Paradigm component based applications

“…While it is an algorithmic concept, its implementation varies quite a lot depending on the execution platform. Hence, we defined a high level master-worker relationship between components [5,4]. While it provides a model close to the abstract concept to the programmers, it can be configured by the execution environment to fit to the actual resources.…”

A DSM-based fragmented data sharing framework for grids

“…In contrast, Spigot provides fine-grained locks to protect blocks of a file, and therefore may improve performance. Juxmem [7][8][9] is somewhat similar to Spigot. Juxmem is also inspired by the DSM approach for transparent access to data and consistency management.…”

“…Moreover, it is not uncommon for scientists to parallelize dataintensive jobs such as climate simulation [1,[7][8][9]2,4,5]. In respect to performance concerns, the original job is usually divided into several sub-jobs which can be executed in parallel.…”

“…Several data grid systems have been proposed [7][8][9][10][11][12][13][14][15][16][17][18][19] to satisfy large scale data-intensive applications. However, most of these systems introduce an explicit scheme for data management [7-9, 18,19], that is, the user himself is left to explicitly store and transfer the necessary data between the replica servers and the computing nodes.…”

“…• Non-transparent access interface Most available data grid systems such as DataMover [13,14], SRB [12,17] and JuxMem [7][8][9] still use an explicit data transfer mechanism or FTP-like protocol that is, the user is required to use an explicit API for locating and transferring files. Such explicit data access schemes forbid legacy applications (i.e.…”