Compare changes very slowly! #1771

New Issue

GiteaMirror · 2025-11-02T04:12:49-06:00

GiteaMirror commented

2025-11-02 04:12:49 -06:00

Originally created by @misterpoesy on GitHub (May 9, 2018).

Gitea version (or commit ref): 1.4.1
Git version: 2.1
Operating system:
Database (use [x]):
- PostgreSQL
- [ x] MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- [x ] Not relevant
Log gist:

Description

When create new pull request, compare two branches very slowly, result to nginx timeout (┬＿┬).
How can i do some optimization?

Screenshots

Originally created by @misterpoesy on GitHub (May 9, 2018).  - Gitea version (or commit ref): 1.4.1 - Git version: 2.1 - Operating system: - Database (use `[x]`): - [ ] PostgreSQL - [ x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x ] Not relevant - Log gist: ## Description When create new pull request, compare two branches very slowly, result to nginx timeout (┬＿┬). How can i do some optimization? ## Screenshots

GiteaMirror added the type/proposal label 2025-11-02 04:12:49 -06:00

GiteaMirror closed this issue

2025-11-02 04:12:49 -06:00

GiteaMirror commented

2025-11-02 04:12:49 -06:00

@rkmax commented on GitHub (May 10, 2018):

I'm using gitea over two weeks running on a t2.small instance. I'm using docker image version 1.4.0 with postgres 9.6 and Git 2.15.0 and nginx as inversed proxy and I'm impress of the performance all is very quickly (I've migrated from gitlab)

here's my docker-compose.yml

version: "3"

networks:
  gitea_app:
    external: false

services:
  gitea_app:
    image: gitea/gitea:1.4.0
    environment:
      - SSH_DOMAIN=yourdomain.com
      - ROOT_URL=https://git.yourdomain.com
      - USER_UID=1000
      - USER_GID=1000
      - RUN_MODE=prod
      - DB_TYPE=postgres
      - DB_HOST=gitea_postgres
      - DB_NAME=gitea
      - DB_USER=gitea
      - DB_PASSWD=gitea
    restart: always
    networks:
      - gitea_app
    volumes:
      - ./gitea_app_data:/data
    ports:
      - "3000:3000"
      - "22:22"
    depends_on:
      - gitea_postgres
  gitea_postgres:
    image: postgres:9.6
    restart: always
    environment:
      - POSTGRES_USER=gitea
      - POSTGRES_PASSWORD=gitea
      - POSTGRES_DB=gitea
    networks:
      - gitea_app
    volumes:
      - ./gitea_postgres_data:/var/lib/postgresql/data
  gitea_web:
    image: nginx:alpine
    restart: always
    volumes:
      - ./gitea_web_data:/etc/nginx/conf.d
      - ./gitea_web_data/cache:/cache
    ports:
      - "80:80"
      - "443:443"
    networks:
      - gitea_app
    depends_on:
      - gitea_app

the only optimization I did was add some cache for static resources on nginx, but nothing more

@rkmax commented on GitHub (May 10, 2018): I'm using gitea over two weeks running on a t2.small instance. I'm using docker image version 1.4.0 with postgres 9.6 and Git 2.15.0 and nginx as inversed proxy and I'm impress of the performance all is very quickly (I've migrated from gitlab) here's my docker-compose.yml ```yaml version: "3" networks: gitea_app: external: false services: gitea_app: image: gitea/gitea:1.4.0 environment: - SSH_DOMAIN=yourdomain.com - ROOT_URL=https://git.yourdomain.com - USER_UID=1000 - USER_GID=1000 - RUN_MODE=prod - DB_TYPE=postgres - DB_HOST=gitea_postgres - DB_NAME=gitea - DB_USER=gitea - DB_PASSWD=gitea restart: always networks: - gitea_app volumes: - ./gitea_app_data:/data ports: - "3000:3000" - "22:22" depends_on: - gitea_postgres gitea_postgres: image: postgres:9.6 restart: always environment: - POSTGRES_USER=gitea - POSTGRES_PASSWORD=gitea - POSTGRES_DB=gitea networks: - gitea_app volumes: - ./gitea_postgres_data:/var/lib/postgresql/data gitea_web: image: nginx:alpine restart: always volumes: - ./gitea_web_data:/etc/nginx/conf.d - ./gitea_web_data/cache:/cache ports: - "80:80" - "443:443" networks: - gitea_app depends_on: - gitea_app ``` the only optimization I did was add some cache for static resources on nginx, but nothing more

GiteaMirror commented

2025-11-02 04:12:50 -06:00

@lunny commented on GitHub (May 10, 2018):

@misterpoesy need more details.

@lunny commented on GitHub (May 10, 2018): @misterpoesy need more details.

GiteaMirror commented

2025-11-02 04:12:50 -06:00

@webjoel commented on GitHub (May 15, 2018):

In my case is a little slow too, repo is very big, an solution is add gauge/loading image for feedback to user. It's possible?

If yes, is good add too in apply merge pull request, what is very slow too e no exixsts feedback to user, only the loading in the browser title.

My repo size is: 1,8 GB.

Issue related: #601

@webjoel commented on GitHub (May 15, 2018): In my case is a little slow too, repo is very big, an solution is add gauge/loading image for feedback to user. It's possible? If yes, is good add too in apply merge pull request, what is very slow too e no exixsts feedback to user, only the loading in the browser title. My repo size is: 1,8 GB. Issue related: #601

GiteaMirror commented

2025-11-02 04:12:50 -06:00

@misterpoesy commented on GitHub (May 22, 2018):

@webjoel Thanks a lot. Issue #601 is my problem.

@misterpoesy commented on GitHub (May 22, 2018): @webjoel Thanks a lot. Issue #601 is my problem.

GiteaMirror commented

2025-11-02 04:12:50 -06:00

@ghost commented on GitHub (Jul 8, 2018):