diff options
author | sina <sina@snix.ir> | 2022-07-30 15:26:52 +0430 |
---|---|---|
committer | sina <sina@snix.ir> | 2022-07-30 15:26:52 +0430 |
commit | 3449c5feab5d27bf395c12a5ad68396412a28577 (patch) | |
tree | aa9125bc395392cce55a47124fb57778b5b034b0 /Readme.md | |
parent | 1069671a171b0fb1a6029534873c3e17dc6e3255 (diff) |
size chunk
Diffstat (limited to 'Readme.md')
-rw-r--r-- | Readme.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -13,9 +13,9 @@ with associated io chunk and io stream interfaces. ### io interfaces: -- **chunkReader**: read and open() data in chunks, there is 4byte + 16byte overhead per chunk. read data can be used safely. this reader has a chunk size in-memory buffer, large chunk size can make application to runs out of memory, thus this is most suitable for sliced data, like network data transmit and so.. +- **chunkReader**: read and open() data in chunks, there is 2byte + 16byte overhead per chunk. read data can be used safely. this reader has a chunk size in-memory buffer, large chunk size can make application to runs out of memory, thus this is most suitable for sliced data, like network data transmit and so.. -- **chunkReader**: seal() and write data in chunks, there is 4byte + 16byte overhead per chunk. this writer has a chunk size in-memory buffer, large chunk size can make application to runs out of memory, thus this is most suitable for sliced data, like network data transmit and so.. +- **chunkReader**: seal() and write data in chunks, there is 2byte + 16byte overhead per chunk. this writer has a chunk size in-memory buffer, large chunk size can make application to runs out of memory, thus this is most suitable for sliced data, like network data transmit and so.. <p align="center"> <img src="https://git.snix.ir/rabaead/plain/chunkio.png" alt="chunkio"/> </p> |