Details

    • Type: Umbrella
    • Status: Open
    • Priority: Blocker
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 3.0.0, 2.2.0
    • Component/s: Performance
    • Labels:
      None

      Description

      How does 2.0.0 compare to old versions? Is it faster, slower? There is rumor that it is much slower, that the problem is the asyncwal writing. Does in-memory compaction slow us down or speed us up? What happens when you enable offheaping?

      Keep notes here in this umbrella issue. Need to be able to say something about perf when 2.0.0 ships.

        Attachments

        1. CAM-CONFIG-V01.patch
          3 kB
          Anastasia Braginsky
        2. flamegraph-1072.1.svg
          1020 kB
          stack
        3. flamegraph-1072.2.svg
          974 kB
          stack
        4. HBase 2.0 performance evaluation - 8GB.pdf
          36 kB
          Eshcar Hillel
        5. HBase 2.0 performance evaluation - 8GB(1).pdf
          58 kB
          Eshcar Hillel
        6. HBase 2.0 performance evaluation - Basic vs None_ system settings.pdf
          36 kB
          Eshcar Hillel
        7. HBase 2.0 performance evaluation - throughput SSD_HDD.pdf
          49 kB
          Eshcar Hillel
        8. HBASE-20188.sh
          2 kB
          Eshcar Hillel
        9. HBASE-20188-xac.sh
          2 kB
          Eshcar Hillel
        10. hbase-env.sh
          8 kB
          stack
        11. hbase-site.xml
          3 kB
          Eshcar Hillel
        12. hbase-site.xml
          8 kB
          stack
        13. hits_with_fp_scheduler.png
          33 kB
          stack
        14. hits.png
          48 kB
          stack
        15. ITBLL2.5B_1.2.7vs2.0.0_cpu.png
          165 kB
          stack
        16. ITBLL2.5B_1.2.7vs2.0.0_gctime.png
          77 kB
          stack
        17. ITBLL2.5B_1.2.7vs2.0.0_iops.png
          40 kB
          stack
        18. ITBLL2.5B_1.2.7vs2.0.0_load.png
          112 kB
          stack
        19. ITBLL2.5B_1.2.7vs2.0.0_memheap.png
          81 kB
          stack
        20. ITBLL2.5B_1.2.7vs2.0.0_memstore.png
          23 kB
          stack
        21. ITBLL2.5B_1.2.7vs2.0.0_ops_NOT_summing_regions.png
          91 kB
          stack
        22. ITBLL2.5B_1.2.7vs2.0.0_ops.png
          56 kB
          stack
        23. lock.127.workloadc.20180402T200918Z.svg
          63 kB
          stack
        24. lock.2.memsize2.c.20180403T160257Z.svg
          99 kB
          stack
        25. perregion.png
          48 kB
          stack
        26. run_ycsb.sh
          7 kB
          stack
        27. total.png
          23 kB
          stack
        28. tree.txt
          985 kB
          stack
        29. workloadx
          3 kB
          Eshcar Hillel
        30. workloadx
          3 kB
          Eshcar Hillel
        31. YCSB_CPU.png
          46 kB
          stack
        32. YCSB_GC_TIME.png
          24 kB
          stack
        33. YCSB_IN_MEMORY_COMPACTION=NONE.ops.png
          31 kB
          stack
        34. YCSB_in-memory-compaction=NONE.ops.png
          28 kB
          stack
        35. YCSB_load.png
          42 kB
          stack
        36. YCSB_MEMSTORE.png
          29 kB
          stack
        37. YCSB_OPs.png
          32 kB
          stack

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                stack stack
              • Votes:
                0 Vote for this issue
                Watchers:
                28 Start watching this issue

                Dates

                • Created:
                  Updated: