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

Posted to dev@phoenix.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2019/06/12 20:23:00 UTC

[jira] [Assigned] (PHOENIX-5340) Set OMID's wait strategy to LOW_CPU for tests

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

Lars Hofhansl reassigned PHOENIX-5340:
--------------------------------------

    Assignee: Lars Hofhansl

> 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
>         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)