Zakelly commented on code in PR #26107: URL: https://github.com/apache/flink/pull/26107#discussion_r1945908802
########## docs/layouts/shortcodes/generated/forst_configurable_configuration.html: ########## @@ -0,0 +1,168 @@ +<table class="configuration table table-bordered"> + <thead> + <tr> + <th class="text-left" style="width: 20%">Key</th> + <th class="text-left" style="width: 15%">Default</th> + <th class="text-left" style="width: 10%">Type</th> + <th class="text-left" style="width: 55%">Description</th> + </tr> + </thead> + <tbody> + <tr> + <td><h5>state.backend.forst.block.blocksize</h5></td> + <td style="word-wrap: break-word;">4 kb</td> + <td>MemorySize</td> + <td>The approximate size (in bytes) of user data packed per block. The default blocksize is '4KB'.</td> Review Comment: 'packed' means that multiple the user's key-values are recorded in one block. For guidance, please check the `large_state_tuning.md` ########## docs/layouts/shortcodes/generated/forst_configurable_configuration.html: ########## @@ -0,0 +1,168 @@ +<table class="configuration table table-bordered"> + <thead> + <tr> + <th class="text-left" style="width: 20%">Key</th> + <th class="text-left" style="width: 15%">Default</th> + <th class="text-left" style="width: 10%">Type</th> + <th class="text-left" style="width: 55%">Description</th> + </tr> + </thead> + <tbody> + <tr> + <td><h5>state.backend.forst.block.blocksize</h5></td> + <td style="word-wrap: break-word;">4 kb</td> + <td>MemorySize</td> + <td>The approximate size (in bytes) of user data packed per block. The default blocksize is '4KB'.</td> + </tr> + <tr> + <td><h5>state.backend.forst.block.cache-size</h5></td> + <td style="word-wrap: break-word;">8 mb</td> + <td>MemorySize</td> + <td>The amount of the cache for data blocks in ForSt. The default block-cache size is '8MB'.</td> Review Comment: For guidance, please check the large_state_tuning.md -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
