You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@rocketmq.apache.org by "Jaskey Lam (JIRA)" <ji...@apache.org> on 2017/07/26 07:58:00 UTC
[jira] [Commented] (ROCKETMQ-245) All topic msg put in the same log
may is not a good desgin .
[ https://issues.apache.org/jira/browse/ROCKETMQ-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101299#comment-16101299 ]
Jaskey Lam commented on ROCKETMQ-245:
-------------------------------------
I am afraid this design is with careful consideration, which helps to improve the write performance when topic is at great numbers.
This is a great improvement when topic numbers is large comparing to Kafka.
> All topic msg put in the same log may is not a good desgin .
> ------------------------------------------------------------
>
> Key: ROCKETMQ-245
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-245
> Project: Apache RocketMQ
> Issue Type: Improvement
> Components: rocketmq-store
> Affects Versions: 4.1.0-incubating
> Reporter: zhaoziyan
> Assignee: yukon
> Priority: Minor
>
> The MQ put all topic msg in the same log file . I think is not a good design .
> Reason : all topic concurrency put msg , they need compete for one file lock, topic may influence each other .
> Some one have change topic msg to store in independent file . The QPS is high than store in the same log file ( The store log system is still include physic log and queue .)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)