services.concurrency config ignored in Hobby Tier?

The following is the output of fly config show (app name and image edited) The services.concurrency sections appear to have no effect. I am running in hobby tier with a single machine (on purpose). I have very lightweight web sockets running and want to avoid the default limit of 25 connections. 25 requests would be plenty.

{
  "app": "zzz",
  "primary_region": "yul",
  "build": {
    "image": "xxx/yyystable"
  },
  "http_service": {
    "internal_port": 8080,
    "force_https": true,
    "auto_stop_machines": false,
    "auto_start_machines": true,
    "min_machines_running": 1,
    "processes": [
      "app"
    ]
  },
  "services": [
    {
      "ports": [
        {
          "port": 80,
          "handlers": [
            "http"
          ],
          "force_https": true
        },
        {
          "port": 443,
          "handlers": [
            "tls",
            "http"
          ]
        }
      ],
      "concurrency": {
        "type": "requests",
        "hard_limit": 50,
        "soft_limit": 45
      }
    }
  ],
  "vm": [
    {
      "cpu_kind": "shared",
      "cpus": 2,
      "memory_mb": 512
    }
  ]
}

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.