Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-5332 Fix slow running Integration Tests
  3. PHOENIX-5340

Set OMID's wait strategy to LOW_CPU for tests

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 4.15.0, 5.1.0
    • None
    • None

    Description

      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!

      Attachments

        1. 5340.txt
          1 kB
          Lars Hofhansl

        Activity

          People

            larsh Lars Hofhansl
            larsh Lars Hofhansl
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: