Skip to content
This repository has been archived by the owner. It is now read-only.
Browse files
address more comments
  • Loading branch information
PepperJo committed Nov 8, 2017
1 parent 0f75d03 commit a5376bb07f67b8fa41854b85a2cbad128bdac97d
Showing 1 changed file with 2 additions and 2 deletions.
@@ -42,10 +42,10 @@ Note that the current prototype implementation supports two ways to store shuffl
data between the stages: (1) shuffle data is stored like in vanilla Spark
in files, (2) data is stored in memory allocated and registered for RDMA transfer.
In constrast, the Crail approach is quite different. Crail was designed as a
In constrast, the Crail approach is different as it was designed as a
storage bus for intermediate data. We believe the Crail's modular architecture
to leverage high-performance storage and networking devices for e.g.
shuffle data has many advantages over a tightly integrated design like
shuffle data has many advantages over a "last-mile" design like
the one described above: no overhead of allocation and registration of data
stored between stages, disaggregation support, seamless support for
different storage types (e.g. RAM, NVMe, ...), tiering, Inter-Job data storage,

0 comments on commit a5376bb

Please sign in to comment.