我正在运行一个停靠的Django应用程序：只有Django + Postgres在本地。当我启动应用程序并转到任何本地主机URL时，它需要长达3-4分钟的时间才能响应。然后它就像预期的那样工作，响应时间为100-200毫秒。

• 有没有沉重的进程运行，它的行为就像不管网址，它可以是管理员， Swagger 或任何其他。
• 在“冻结”期间，它会明显地加载我的CPU。我在一台非常旧的机器上遇到这个问题已经有一段时间了，我认为这只是因为它太旧了，但我刚刚在一台全新的机器上测试过，它也有同样的问题，所以不是硬件问题。
• 部署和URL/API测试不受此影响，并且不会冻结。
• 尽管应用未响应任何HTTP请求，但使用docker-compose exec或~run执行任何命令仍能按预期工作。
• PS：我可以添加线程转储或任何其他日志，如果必要的话，我真的不知道在哪里寻找问题的根源。*

下面是我的.yml文件内容，以防它可能是罪魁祸首：

version: '3'

volumes:
  backend_local_postgres_data: {}
  backend_local_postgres_data_backups: {}

services:
  django: &django
    build:
      context: .
      dockerfile: ./compose/local/django/Dockerfile
    image: backend_local_django
    container_name: backend_local_django
    depends_on:
      - postgres
    volumes:
      - .:/app:z
    env_file:
      - ./.envs/.local/.django
      - ./.envs/.local/.postgres
    ports:
      - "8000:8000"
    command: /start

  postgres:
    build:
      context: .
      dockerfile: ./compose/production/postgres/Dockerfile
    image: backend_production_postgres
    container_name: backend_local_postgres
    volumes:
      - backend_local_postgres_data:/var/lib/postgresql/data:Z
      - backend_local_postgres_data_backups:/backups:z
    env_file:
      - ./.envs/.local/.postgres

应用程序启动日志，如几个答案中所要求的：

(venv) docker-compose -f local.yml up
[+] Running 1/1
 - Network backend_default  Created                                                                                                                                                                                          0.6s 
[+] Running 3/34T19:42:41+01:00" level=warning msg="mount of type `volume` should not define `bind` option"
 - Network backed_default            Created                                                                                                                                                                                0.6s
 - Container backend_local_postgres  Created                                                                                                                                                                                0.1s
 - Container backend_local_django    Created                                                                                                                                                                                0.1s
Attaching to backend_local_django, backend_local_postgres
| 
| PostgreSQL Database directory appears to contain a database; Skipping initialization
| 
| 2023-02-04 18:42:42.783 UTC [1] LOG:  starting PostgreSQL 14.6 (Debian 14.6-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
| 2023-02-04 18:42:42.783 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
| 2023-02-04 18:42:42.783 UTC [1] LOG:  listening on IPv6 address "::", port 5432
| 2023-02-04 18:42:42.792 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
| 2023-02-04 18:42:42.804 UTC [27] LOG:  database system was shut down at 2023-02-01 11:55:22 UTC
| 2023-02-04 18:42:42.814 UTC [1] LOG:  database system is ready to accept connections
| PostgreSQL is available
| Operations to perform:
|   Apply all migrations: account, admin, auth, authtoken, constructor, contenttypes, django_celery_beat, sessions, sites, socialaccount, users
| Running migrations:      
|   No migrations to apply.
| WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
|  * Running on all addresses (0.0.0.0)
|  * Running on http://127.0.0.1:8000  
|  * Running on http://172.18.0.3:8000 
| Press CTRL+C to quit
|  * Restarting with watchdog (inotify)
| Performing system checks...
| 
| System check identified no issues (0 silenced).
| 
| Django version 4.0.8, using settings 'config.settings.local'
| Development server is running at http://0.0.0.0:8000/
| Using the Werkzeug debugger (http://werkzeug.pocoo.org/)
| Quit the server with CONTROL-C.
|  * Debugger is active!
|  * Debugger PIN: 130-235-671

如果问题可能与我正在使用的某个库有关，下面也是我的requirements.txt：
一个二个一个一个