You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@rocketmq.apache.org by "vongosling (JIRA)" <ji...@apache.org> on 2017/12/13 09:28:00 UTC

[jira] [Updated] (ROCKETMQ-91) Reduce lock granularity for putMessage to get better performance

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

vongosling updated ROCKETMQ-91:
-------------------------------
    Summary: Reduce lock granularity for putMessage to get better performance  (was: 4.2)

> Reduce lock granularity for putMessage to get better performance
> ----------------------------------------------------------------
>
>                 Key: ROCKETMQ-91
>                 URL: https://issues.apache.org/jira/browse/ROCKETMQ-91
>             Project: Apache RocketMQ
>          Issue Type: Improvement
>    Affects Versions: 4.1.0-incubating
>            Reporter: dongeforever
>            Assignee: dongeforever
>             Fix For: 4.2.0
>
>
> CommitLog putMessage has a lock as:
> lockForPutMessage()
> ....
> releasePutMessageLock()
> The logic inside the lock includes two main operations:
> 1 encode the message
> 2 write to the PageCache.
> However, we can take the first operation(encode message) out from the lock to achieve better performance.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)