2012 SC Companion: High Performance Computing, Networking Storage and Analysis 2012
DOI: 10.1109/sc.companion.2012.17
|View full text |Cite
|
Sign up to set email alerts
|

An Evolutionary Path to Object Storage Access

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2013
2013
2022
2022

Publication Types

Select...
4
1
1

Relationship

1
5

Authors

Journals

citations
Cited by 6 publications
(3 citation statements)
references
References 16 publications
0
3
0
Order By: Relevance
“…In many cases, however, POSIX is unnecessarily strict (Kimpe and Ross, 2014). It may hurt the system’s scalability and the ability to control the small objects contained in a file independently (Goodell et al, 2012). Object-based systems and KVStores provide better flexibility with an object-based interface, instead of the file-based interface.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…In many cases, however, POSIX is unnecessarily strict (Kimpe and Ross, 2014). It may hurt the system’s scalability and the ability to control the small objects contained in a file independently (Goodell et al, 2012). Object-based systems and KVStores provide better flexibility with an object-based interface, instead of the file-based interface.…”
Section: Related Workmentioning
confidence: 99%
“…Many works have compared the advantages and disadvantages of file systems and object storage systems (Brim et al, 2013; Gibson et al, 1996; Group, 2012). Other works have tried to integrate PFSs and object storage systems (Devulapalli et al, 2007) or expose the underlying object data streams of a PFS (Goodell et al, 2012) to gain better I/O performance. This study explores whether HPC workloads can benefit from an object-based system such as KVStore.…”
Section: Related Workmentioning
confidence: 99%
“…Recently, the "end-of-files" (EOF) [15] extension to the Parallel Virtual File System (PVFS) [7] was created to expose the object storage abstraction directly into the client space, presenting a file as a set of distinct, physically distributed objects that applications forward requests directly to, as opposed to a more implicit mapping via a striping function. Each object has an independent address space, potentially simplifying the layout of complex datasets.…”
Section: Eof Data Managementmentioning
confidence: 99%