Release Notes
Announcements
fs.ofs.block.memory.trunk.byte.Configuration Item | Configuration Item Content | Description |
fs.ofs.block.memory.trunk.byte | 1048576 | Object block size in bytes. The default value is 1048576 (1 MB). |
fs.cosn.trsf before the configuration item name, such as fs.cosn.trsf.fs.ofs.prev.read.block.count.Configuration Item | Configuration Item Content | Description |
fs.ofs.prev.read.block.count | 16 | Pre-read block count, default value: 16 |
fs.ofs.prev.read.block.release.enable | true | Whether to release read blocks from memory, default value: true |
fs.ofs.block.max.read.memory.cache.mb | 16 | Single file available memory amount, default value: 16, unit: MB Note: To avoid OOM, you can refer to the following context for memory usage practice and control the global cache model. |
fs.ofs.data.transfer.thread.count | 32 | Core thread count of the IO thread pool for prefetching blocks from the bucket |
fs.ofs.data.transfer.max.thread.count | Integer.MAX_VALUE | Maximum number of threads in the IO thread pool |
fs.ofs.block.memory.trunk.byte based on actual business scenarios, modify the data size read from the COS bucket each time, and avoid read amplification in random read scenarios.Configuration Item | Configuration Item Content | Description |
fs.ofs.block.max.memory.cache.mb | 16 | Memory cache usage, default value: 16, unit: MB |
fs.ofs.block.max.file.cache.mb | 256 | Disk cache usage, default value: 256, unit: MB |
fs.cosn.trsf before the configuration item name, such as fs.cosn.trsf.fs.ofs.block.max.memory.cache.mb.Configuration Item | Configuration Item Content | Description |
fs.ofs.block.total.memory.cache.mb | 0 | Maximum upload memory usage, default value 0 (no control), MB |
fs.ofs.block.total.memory.cache.percent | 100 | Maximum upload memory usage ratio, default value 100, unit: percentage |
fs.ofs.block.total.memory.jvm.heap.percent | 0 | Maximum JVM memory usage ratio, default value 0 (no control), unit: percentage |
fs.ofs.block.total.memory.cache.mb and fs.ofs.block.total.memory.cache.percent. After configuration, the maximum memory size used is: fs.ofs.block.total.memory.cache.mb * fs.ofs.block.total.memory.cache.percent / 100. Once configured, the SDK will calculate the number of files that can be written concurrently based on the global memory cache size / the maximum size of a single file fs.ofs.block.max.memory.cache.mb, and allocate semaphores accordingly. When opening a new file, it will apply for one semaphore. If the application fails, it will forcibly use disk cache. When the file is closed, the semaphore will be returned. (ManagementFactory.getMemoryMXBean().getHeapMemoryUsage().getMax()) * fs.ofs.block.total.memory.jvm.heap.percent / 100 to determine.fs.ofs.block.total.memory.cache.mb and fs.ofs.block.total.memory.jvm.heap.percent are set to 0, meaning no memory control is performed. If both configuration items are non-zero, rule 1 (maximum memory usage) has a higher priority than rule 2 (maximum JVM memory usage).Configuration Item | Configuration Item Content | Description |
fs.ofs.block.total.read.memory.cache.mb | 0 | Maximum download memory usage, default value 0 (no control), MB |
fs.ofs.block.total.read.memory.cache.percent | 100 | Maximum download memory usage ratio, default value 100, unit: percentage |
fs.ofs.block.total.read.memory.cache.mb and fs.ofs.block.total.read.memory.cache.percent. After configuration, the maximum memory used is: fs.ofs.block.total.read.memory.cache.mb * fs.ofs.block.total.read.memory.cache.percent / 100. Once configured, the SDK calculates the number of files that can be written simultaneously based on the global memory cache size divided by the maximum size of a single file fs.ofs.block.max.memory.cache.mb, thereby allocating signals. When opening a new file, it requests one semaphore. If the request fails, it forcibly uses disk cache. When a file is closed, the semaphore is returned. The request implements a blocking mechanism through queuing. When semaphores are insufficient, it waits for other files to close and release semaphores.Esta página foi útil?
Você também pode entrar em contato com a Equipe de vendas ou Enviar um tíquete em caso de ajuda.
comentários