[
https://issues.apache.org/jira/browse/PHOENIX-5340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16862938#comment-16862938
]
Hudson commented on PHOENIX-5340:
---------------------------------
FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #429 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.3/429/])
PHOENIX-5340 Set OMID's wait strategy to LOW_CPU for tests. (larsh: rev
54793248ef8ec3cf96d2eedce0ea04d7b655d8f1)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/transaction/OmidTransactionProvider.java
> Set OMID's wait strategy to LOW_CPU for tests
> ---------------------------------------------
>
> Key: PHOENIX-5340
> URL: https://issues.apache.org/jira/browse/PHOENIX-5340
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Priority: Major
> Fix For: 4.15.0, 5.1.0
>
> Attachments: 5340.txt
>
>
> OMID has a LOW_CPU and a HIGH_THROUGHPUT wait strategy (using a disruptor).
> HIGH_THROUGHPUT does busy waiting, and I'd argue even in production is not
> the way to run it unless you have a dedicated machine/vm for the TSO.
> For tests it's quite bad, as the disruptor will keep a few cores 100% busy!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
