Uploaded image for project: 'Indy Node'
  1. Indy Node
  2. INDY-1721

Memory Leak Issues

    XMLWordPrintable

    Details

    • Type: Epic
    • Status: Complete
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Epic Name:
      Memory Leak Issues
    • Documentation Impact:
      Unset

      Description

      • Check results of the latest load testing where we fail with out of memory
      • Check if it depends on
        • txn type
        • logging
        • metrics
        • ZMQ
      • Try more profiling

       

      Plan of attack

      1. Run more load tests with different txn types and metrics
      2. Run python profiler to check if there are any leaks in our main code
      3. Limit ZMQ watermarks to some small number
      4. Check if number of client connections affects memory consumption
      5. Try to reset ZMQ listener stacks to see if memory usage decreases
      6. Limit RocksDB memory usage in config
      7. Use leveldb instead of RocksDB for all storages
      8. Use file storage instead of LevelDB/RocksDB
      9. Valgrind

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            ashcherbakov Alexander Shcherbakov
            Watchers:
            Alexander Shcherbakov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: