[
https://issues.apache.org/jira/browse/OMID-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407279#comment-15407279
]
Francisco Perez-Sorrosal commented on OMID-50:
----------------------------------------------
I think you have done the changes on top of the branch 0.8.2.0 instead of the
current master. I've tried to apply the patch on the current master but it is
not applied correctly. I´ve checked the contents and you made some changes in
the /tso-server/src/main/resources/default-omid.yml file which does not exist
anymore in master (now is
/tso-server/src/main/resources/default-omid-server-configuration.yml) what
means that you probably did the changes on the wrong branch.
> Provide an option to reduce tso-server CPU usage
> ------------------------------------------------
>
> Key: OMID-50
> URL: https://issues.apache.org/jira/browse/OMID-50
> Project: Apache Omid
> Issue Type: Improvement
> Reporter: Daniel Dai
> Assignee: Daniel Dai
> Fix For: 0.8.3.0
>
> Attachments: OMID-50-1.patch
>
>
> Currently tso-server use 300% cpu even at idle time. The reason for this 300%
> cpu usage is due to the BusyWaitStrategy used in disruptor. While this is
> good for throughput, it wastes resources in many use cases. In this ticket, I
> provide a config to use a different wait strategy and reduce the cpu usage
> with the option on.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
