dockerzhang opened a new issue #724:
URL: https://github.com/apache/incubator-inlong/issues/724
<p>3. The number of memory cache blocks should be configurable: the current
memory cache is managed according to the fixed configuration of 2 memory blocks
per topic. We should allow the business to build more memory cache space based
on actual resource conditions;</p>
<p>------------------------------------------------------------------------</p>
<p>I plan to improve the content of this piece like this:<br/>
<span class="image-wrap" style=""><img
src="https://issues.apache.org/jira/secure/attachment/13003169/13003169_screenshot-1.png";
style="border: 0px solid black" /></span> </p>
<p>I plan to change the memory for receiving messages from the current fixed
2 blocks to multiple blocks and use them recyclely:<br/>
The number of blocks and the size of each block in the memory pool is
configurable, with a minimum of 2 blocks, with a minimum of 1M; after the
memory block is full or triggered, it will switch to the next block of memory
to continue reading and writing; memory pool storage combined with improved <a
href="https://issues.apache.org/jira/browse/INLONG-120"; title="Aligned disk
data storage" class="issue-link" data-issue-key="INLONG-120">TUBEMQ-120</a> and
<a href="https://issues.apache.org/jira/browse/INLONG-123"; title="Batch flush
data to disk" class="issue-link"
data-issue-key="INLONG-123"><del>TUBEMQ-123</del></a> to write the data in the
memory to the disk in an asynchronous batch flushing mode. The overflow
failures will be return to the requests if there is no free memory block
currently available for switching.</p>
<p>After this adjustment, it is very convenient for the system where the
number of topics in the system is very small but the memory is very rich, and
the system's short-term anti-peak ability is also increased.</p>
<i>JIRA link - <a
href="https://issues.apache.org/jira/browse/INLONG-125";>[INLONG-125]</a>
created by gosonzhang</i>
--
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]
![https://issues.apache.org/jira/secure/attachment/13003169/13003169_screenshot-1.png"](https://issues.apache.org/jira/secure/attachment/13003169/13003169_screenshot-1.png"){kind=link}