New Metabase Very Slow 53.2 / PostgreSQL / AWS

Get Help
1

Just installed Metabase on AWS using Docker with:

  • ALB and target gruops
  • EC2 instance is a t2.small which still has 70% CPU to spare.
  • Using PostgreSql for the metabase db.
  • Using RDS as the service and it's a comfortably large DB class.

I only have 4 questions written which query an Aurora MySQL within the same VPC. The Metabase pages load up to 2 minutes before completing. Sometimes it times out. My troubleshooting data is below. The connection to PostgreSQL from the EC2 terminal is spot on an so is our production DB.

{
  "browser-info": {
    "language": "en-US",
    "platform": "MacIntel",
    "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36",
    "vendor": "Google Inc."
  },
  "metabase-info": {
    "databases": [
      "mysql"
    ],
    "run-mode": "prod",
    "plan-alias": "",
    "version": {
      "date": "2025-02-11",
      "tag": "v0.53.2",
      "hash": "57fd127"
    },
    "settings": {
      "report-timezone": "America/Detroit"
    },
    "hosting-env": "unknown",
    "application-database": "postgres",
    "application-database-details": {
      "database": {
        "name": "PostgreSQL",
        "version": "16.3"
      },
      "jdbc-driver": {
        "name": "PostgreSQL JDBC Driver",
        "version": "42.7.4"
      }
    }
  },
  "system-info": {
    "file.encoding": "UTF-8",
    "java.runtime.name": "OpenJDK Runtime Environment",
    "java.runtime.version": "21.0.6+7-LTS",
    "java.vendor": "Eclipse Adoptium",
    "java.vendor.url": "https://adoptium.net/",
    "java.version": "21.0.6",
    "java.vm.name": "OpenJDK 64-Bit Server VM",
    "java.vm.version": "21.0.6+7-LTS",
    "os.name": "Linux",
    "os.version": "5.10.233-224.894.amzn2.x86_64",
    "user.language": "en",
    "user.timezone": "GMT"
  }
}
2

Use at least a t3g.medium

1 Like
3

I didn't see any T3g but they do have T4g. Could try that. Will report results.

4

Just tried an m5a.large instance and it's still taking a long time to connect to the site. I'm beginning to think it's DNS or something. This may be a dumb question but is there a reason you can't load your docker into port 80 instead of 3000 as the docs suggest?

5

You should use a reverse proxy for that

1 Like
6

@Luiggi I was confused. I'm using an Application Load Balancer that is handling the routing to port 3000 on the web server. It did have to remove a listener because I made a mistake. Testing to see if that was causing any delay.