A grid-enabled software distributed shared memory system on a wide area network

Liang, Tyng-Yeu; Wu, Chang-Luen; Shieh, Ce-Kuen; Chang, Jyh-Biau

doi:10.1016/j.future.2006.10.003

Cited by 15 publications

(15 citation statements)

References 28 publications

(23 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…4 displays the Spigot architecture, which consists of three modules, namely SUTIL (spigot utility module), SFS (spigot file system module) and SFPS (spigot fragments publishing service module). In addition, Spigot adopts Teamster-G [28][29][30][31], FUSE [34] and Globus RLS (Replica Location Service) [22] as sub-systems.…”

Section: Methodsmentioning

confidence: 99%

“…On the other hand, strategies for transparently maintaining data consistency have been widely studied in the context of DSM systems. Although the design of most available DSM systems is acceptable only in a small scale environment, advanced DSM systems [28][29][30][31] have been proposed for the grid environment. Spigot consequently adopts a page-based, gridenabled DSM system, namely Teamster-G [28][29][30][31] as a sub-system.…”

Section: A Guarantee Of Replica Consistencymentioning

confidence: 99%

“…The DSM system makes the virtual address spaces of the distributed nodes look like a single shared memory with a unique address space, namely a virtual global memory image (GMI) [28][29][30][31]. All node accesses to a shared page of the virtual GMI are detected by page protection with protection states such as invalid, read-only and read/write.…”

Section: A Guarantee Of Replica Consistencymentioning

confidence: 99%

“…To maintain the data consistency of modified fragments, Spigot adopts a page-based, grid-enabled Distributed Shared Memory (DSM) system, namely Teamster-G [28][29][30][31], to support fragment-level transfer on-demand. Spigot maps the contents of fragments into the DSM space and relies on the DSM system to transparently share data with concern for consistency.…”

Section: Introductionmentioning

confidence: 99%

“…Spigot maps the contents of fragments into the DSM space and relies on the DSM system to transparently share data with concern for consistency. It inherits a release data consistency model [28,30,31] from Teamster-G and therefore does not bother the users with the consistency of shared data.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

A DSM-based fragmented data sharing framework for grids

Chen

Chang

Shieh

et al. 2010

Future Generation Computer Systems

Self Cite

View full text Add to dashboard Cite

Section: Methodsmentioning

confidence: 99%

Section: A Guarantee Of Replica Consistencymentioning

confidence: 99%

Section: A Guarantee Of Replica Consistencymentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

A DSM-based fragmented data sharing framework for grids

Chen

Chang

Shieh

et al. 2010

Future Generation Computer Systems

Self Cite

View full text Add to dashboard Cite

On‐demand data co‐allocation with user‐level cache for grids

Chen

Chang

et al. 2010

Concurrency and Computation

Self Cite

View full text Add to dashboard Cite

SUMMARYConventional remote data access middlewares usually provide client applications with either a pre-staging scheme or an on-demand access scheme to fetch data. The pre-staging scheme uses parallel downloads to fetch a completed input file from multiple data sources, even when only a tiny file fragment is required. Such a transfer scheme consumes unnecessary data transmission time and storage space. In contrast, the on-demand scheme downloads only the required data blocks from a single data source and does not fully utilize the downstream bandwidth of the computing nodes. This paper presents a middleware called 'Spigot' that facilitates legacy (grid-unaware) applications to transparently access remote data by using native I/O function calls. Spigot uses the on-demand concept to avoid unnecessary data transfer and adopts a co-allocation download algorithm to improve the data transfer performance. Moreover, it uses the pre-fetching strategy to reduce the data waiting time by overlapping data acquisition and data processing. It also provides the client application with its own user-level cache, which is advantageous since a larger cache space is available in comparison with the kernel-level cache. Further, it is easy to maintain data consistency between Spigot nodes. The experimental results indicate that Spigot achieves superior performance in reducing the data waiting time than the pre-staging and the on-demand access schemes.

show abstract