Skip to content

Commit ba1d26a

Browse files
committed
adds in block file description
1 parent 24380d9 commit ba1d26a

File tree

1 file changed

+4
-5
lines changed
  • hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws

1 file changed

+4
-5
lines changed

hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/prefetching.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,7 @@ caches these blocks.
2828
### Basic Concepts
2929

3030
* **Remote File**: A binary blob of data stored on some storage device.
31+
* **Block File**: Local file containing a block of the remote file.
3132
* **Block**: A file is divided into a number of blocks. The size of the first n-1 blocks is same,
3233
and the size of the last block may be same or smaller.
3334
* **Block based reading**: The granularity of read is one block. That is, either an entire block is
@@ -81,7 +82,7 @@ blocks of 64KB.
8182
access to the current buffer in use.
8283

8384
`SingleFilePerBlockCache` - Responsible for caching blocks to the local file system. Each cache
84-
block is stored on the local disk as a separate file.
85+
block is stored on the local disk as a separate block file.
8586

8687
### Operation
8788

@@ -181,7 +182,5 @@ For the above read sequence, when the `seek(10MB)` call is issued, block 0 has n
181182
completely so cache it as the caller will probably want to read from it again.
182183

183184
When `seek(2MB)` is called, the position is back inside block 0. The next read can now be satisfied
184-
from the locally cached block, which is typically orders of magnitude faster than a network based
185-
read.
186-
187-
185+
from the locally cached block file, which is typically orders of magnitude faster than a network
186+
based read.

0 commit comments

Comments
 (0)