[
https://issues.apache.org/jira/browse/OMID-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414721#comment-15414721
]
ASF GitHub Bot commented on OMID-50:
------------------------------------
Github user francisco-perez-sorrosal commented on a diff in the pull request:
https://github.com/apache/incubator-omid/pull/3#discussion_r74187443
--- Diff:
tso-server/src/main/java/org/apache/omid/tso/RetryProcessorImpl.java ---
@@ -69,7 +72,8 @@
private final Meter noCTFoundMeter;
@Inject
- RetryProcessorImpl(MetricsRegistry metrics,
+ RetryProcessorImpl(@Named("PersistenceStrategy") WaitStrategy strategy,
--- End diff --
Typo in named. Should be the same name that is in the DisruptorModule.java
for the retry processor:
```
@Named("RetryStrategy")
```
> 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.2.10
>
> 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)
