Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.15.0, 5.1.0
    • Labels:
      None

      Description

      I noticed that 95% of the time is spent in testLocalIndexScanAfterRegionSplit.

      In that test we split the table 4 times, and each time wait until the parent region is remove (in a major compaction).

      The test is just as valid if we split the table only twice. That effectively cuts almost 50% off the runtime. Since we test for the number of a chunks we have in the explain plan, I cannot do the same trick I did in PHOENIX-5336.

        Attachments

        1. 5377.txt
          0.9 kB
          Lars Hofhansl

          Activity

            People

            • Assignee:
              lhofhansl Lars Hofhansl
              Reporter:
              lhofhansl Lars Hofhansl
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: