• Sean McGivern's avatar
    Stop recording connection pool metrics for load balancing hosts · 40802e2a
    Sean McGivern authored
    The cardinality of these is simply too high: for a single (Rails) host
    on GitLab.com, we have 384 elements due to a combination of:
    
    1. Puma threads.
    2. Load balancing hosts.
    3. Load balancing ports.
    
    Realistically, the saturation for a load balancing connection pool
    should never be higher than for ActiveRecord::Base anyway.
    40802e2a
gitlab_metrics.md 34.3 KB