February 14, 2022, incluxdb survey - mind map

Abstract :

Show right... In the form of brain map influxdb The research of , Use tree structure to associate relevant modules , 

The purpose is to facilitate the brain to understand and store

Brain map :

Influxdb research
  Storage
    1. Storage engine technology roadmap
      1. LSM
        1. levelDB
          1. Cannot hot backup
          2. The open file handle exceeds the upper limit
        2. rocksDB
          1. Repair hot backup
          2. The open file handle exceeds the upper limit
      2. B+ Trees
        1. Bolt
          1. B+
            1. Only one file handle
            2. Conducive to continuous writing
            3. A large number of sequential databases are written discontinuously
              1. Cause the disk to write randomly
              2. Affect write performance
          2. mmap
            1. Reduced kernel buffer
            2. disk IO
        2. Optimize
          1. increase WAL layer
            1. Preprocessing key Merge write
              1. Reduce the number of writes
              2. The random write problem still exists
      3. TSM
        1. Since the research LSM variant
          1. solve B+ Tree random write performance problem
          2. Write from now on WAL Layer increases confidence in development capabilities
        2. increase WAL layer
        3. Improved number of open file handles
    2. TSM
  Distributed
    1. colony
      1. influxdb official
        1. cluster Closed source
        2. Provide relay
          1. Lightweight agents
            1. The service node is still a single node
            2. Use the front-end agent to realize multi node writing
          2. No dispersion key The strategy of
            1. Can't scale horizontally
      2. Open source community alternatives
        1. freetsdb
          1. from influxdb1.8.6 Version transformation
          2. Built in cluster feature
          3. Ecological compatibility
            1. The interface layer
            2. Function layer
            3. Internal implementation layer
    2. High availability
      1. freetsdb
        1. hinted-handoff
          1. Write other nodes through this node
          2. Other nodes are down
          3. Write data to this node
          4. Write to other nodes after other nodes recover
  demand
    1. functional requirement
      1. Write according to the time point
      2. Write only, do not update
      3. Data with time can be deleted automatically
      4. Do not handle frequent deletions
    2. Performance requirements
      1. Hardware standard
        1. disk IO
        2. CPU Main frequency
      2. Performance requirement index
        1. Write QPS
        2. read QPS
        3. Memory footprint
        4. Disk usage
        5. CPU Occupy