[ 
https://issues.apache.org/jira/browse/TUBEMQ-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guocheng Zhang updated TUBEMQ-123:
----------------------------------
    Description: 
4. More effective memory-to-disk operation: At present, the flashing operation 
is to flash messages from the memory to the disk one by one for storage. This 
block can be adjusted to write to the disk in batches according to the memory 
block, thereby improving storage efficiency;

 

------------------------------------------------------

This problem was pointed out by an MQ expert: in the current version, TubeMQ 
does not handle the data well enough when refreshing the data from memory to 
disk, It is carried out through the refresh mode one by one, the related 
problems are shown in the following figure:

!image-2020-05-16-21-56-43-218.png!

 

 

  was:4. More effective memory-to-disk operation: At present, the flashing 
operation is to flash messages from the memory to the disk one by one for 
storage. This block can be adjusted to write to the disk in batches according 
to the memory block, thereby improving storage efficiency;


> Batch flush data to disk
> ------------------------
>
>                 Key: TUBEMQ-123
>                 URL: https://issues.apache.org/jira/browse/TUBEMQ-123
>             Project: Apache TubeMQ
>          Issue Type: Sub-task
>            Reporter: Guocheng Zhang
>            Priority: Major
>         Attachments: image-2020-05-16-21-56-43-218.png
>
>
> 4. More effective memory-to-disk operation: At present, the flashing 
> operation is to flash messages from the memory to the disk one by one for 
> storage. This block can be adjusted to write to the disk in batches according 
> to the memory block, thereby improving storage efficiency;
>  
> ------------------------------------------------------
> This problem was pointed out by an MQ expert: in the current version, TubeMQ 
> does not handle the data well enough when refreshing the data from memory to 
> disk, It is carried out through the refresh mode one by one, the related 
> problems are shown in the following figure:
> !image-2020-05-16-21-56-43-218.png!
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to