Skip to content

Compare changes very slowly! #3926

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
5 tasks
misterpoesy opened this issue May 9, 2018 · 5 comments
Closed
5 tasks

Compare changes very slowly! #3926

misterpoesy opened this issue May 9, 2018 · 5 comments
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@misterpoesy
Copy link

  • 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

@lafriks lafriks added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label May 9, 2018
@rkmax
Copy link

rkmax commented 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

@lunny
Copy link
Member

lunny commented May 10, 2018

@misterpoesy need more details.

@webjoel
Copy link
Contributor

webjoel commented 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

@misterpoesy
Copy link
Author

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

@ghost
Copy link

ghost commented Jul 8, 2018

My repo size is: 1,8 GB.

@webjoel oof looks like a job for https://rtyley.github.io/bfg-repo-cleaner/

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

5 participants