github.com/go-graphite/carbonapi@v0.17.0/.github/ISSUE_TEMPLATE/performance-issues-questions.md (about)

     1  ---
     2  name: Performance issues/questions
     3  about: Any questions or issues related to performance (CPU Usage, Query time, Memory
     4    usage)
     5  title: "[Performance]"
     6  labels: performance
     7  assignees: ''
     8  
     9  ---
    10  
    11  **Problem description**
    12  In as much details as possible, please explain what's the problem. E.x. My query X runs Y seconds, instead of Z seconds?
    13  
    14  **carbonapi's version**
    15  Version of carbonapi. If you build your own packages, what golang version are you using?
    16  
    17  **Does this happened before**
    18  In case same queries ran fine before - please provide a version of carbonapi that didn't had that problems.
    19  
    20  **carbonapi's config**
    21  Configuration file of carbonapi.
    22  
    23  **backend software and config**
    24  What are you running on backend? What it's version? Config for the backend?
    25  
    26  **carbonapi performance metrics**
    27  1. Please enable `expvars` in the config and provide it's output
    28  2. What's system load on a server? What's the memory consumption?
    29  3. If possible, please provide profiler's output (https://blog.golang.org/pprof for instruction how to do that, `debug` handlers can be enabled in carbonapi's config on a separate port). Golang allows different types of profiles. It's always better to give CPU Profile, Memory profile and Lock profile, but that depends on what's the symptoms.
    30  4. Debug logs could be helpful as well
    31  
    32  **Query that causes problems**
    33  1. What's the query?
    34  2. How many metrics does it fetch?
    35  3. What's the resolution of those metrics? If it's not consistent (e.x. different metrics have different resolution) please specify that and provide average metric resolution
    36  4. How many datapoints per metric do you have?
    37  
    38  **Additional context**
    39  Add any other context or screenshots about the feature request here.