2009
DOI: 10.1007/978-3-642-03869-3_40
|View full text |Cite
|
Sign up to set email alerts
|

Enabling High Data Throughput in Desktop Grids through Decentralized Data and Metadata Management: The BlobSeer Approach

Abstract: Abstract. Whereas traditional Desktop Grids rely on centralized servers for data management, some recent progress has been made to enable distributed, large input data, using to peer-to-peer (P2P) protocols and Content Distribution Networks (CDN). We make a step further and propose a generic, yet efficient data storage which enables the use of Desktop Grids for applications with high output data requirements, where the access grain and the access patterns may be random. Our solution builds on a blob management… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
15
0

Year Published

2010
2010
2015
2015

Publication Types

Select...
5
1
1

Relationship

4
3

Authors

Journals

citations
Cited by 15 publications
(15 citation statements)
references
References 12 publications
0
15
0
Order By: Relevance
“…This is crucial in achieving a high aggregated throughput for dataintensive applications, as demonstrated by our previous work [13][14][15].…”
Section: Key Featuresmentioning
confidence: 99%
See 1 more Smart Citation
“…This is crucial in achieving a high aggregated throughput for dataintensive applications, as demonstrated by our previous work [13][14][15].…”
Section: Key Featuresmentioning
confidence: 99%
“…-We apply our proposal to improve BlobSeer [13][14][15], a data management service specifically designed to address the needs of data-intensive applications. -We perform extensive experimentations on the Grid5000 testbed [11] in order to demonstrate the benefits of our approach.…”
Section: Introductionmentioning
confidence: 99%
“…Second, we propose a generalization for a set of versioning algorithms for data management we initially introduced in [21,22]. We have introduced new data structures and redesigned several aspects to account for better decentralized management, asynchrony, fault tolerance and last but not least allow the user to explicitly control written data layout such that it is optimally distributed for reading.…”
Section: Contributionmentioning
confidence: 99%
“…The typical size for a page within a blob can be smaller that 1 MB, whence the challenge of dealing with hundreds of thousands of pages belonging to just one BLOB. BlobSeer provides efficient support for heavily-concurrent accesses to the stored data, reaching a throughput of 6.7 GB/s aggregated bandwidth for a configuration with 60 metadata providers, 90 data providers and 360 concurrent writers, as explained in [11].…”
Section: Blobseermentioning
confidence: 99%
“…Dynamic dimensioning: Extensive performance evaluations [11] carried out for BlobSeer reveal that the aggregate bandwidth of concurrent WRITE or READ operations grows as the number of data providers and metadata providers increases. However, deploying BlobSeer's providers on a large number of physical nodes can be an expensive approach, and their optimum number is often unpredictable, as it depends on the load of the providers and on the number of clients concurrently accessing them.…”
Section: A Self-adaptation: What To Adapt?mentioning
confidence: 99%