Details

    • Type: Task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Fix Version/s: 0.6.3
    • Component/s: None
    • Labels:
      None

      Description

      I suggested this in a ML thread but it seems that nobody actually tried it. I think it's worth following up on:

      You could try setting the compaction thread to a lower priority. You could add a thread priority to NamedThreadPool, and pass that up from CompactionExecutor constructor. According to http://www.javamex.com/tutorials/threads/priority_what.shtml you have to run as root and add a JVM option to get this to work.

      In particular, Brandon saw stress.py read latencies spike to 100ms during [anti]compaction on a 2 core machine. I'd like to see if this can mitigate that.

        Attachments

        1. stats.txt
          4 kB
          Edward Capriolo
        2. CompactionManager.java
          24 kB
          Edward Capriolo
        3. 1181-trunk.txt
          4 kB
          Brandon Williams
        4. 1181.txt
          3 kB
          Jonathan Ellis

          Activity

            People

            • Assignee:
              brandon.williams Brandon Williams
              Reporter:
              jbellis Jonathan Ellis
              Reviewer:
              Jonathan Ellis
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: