github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Compare changes and new pull requests take a very long time. #1204

New Issue
Closed
opened 2025-11-02 03:52:19 -06:00 by GiteaMirror · 18 comments
GiteaMirror commented 2025-11-02 03:52:19 -06:00
Owner
Copy Link

Originally created by @MsBuggy on GitHub (Nov 3, 2017).

  • Gitea version (or commit ref): 1.2 windows-amd64
  • Git version: 2.11.0 windows
  • Operating system: windows 2008 R2 16 CPU cores and 16GB RAM
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

I try to create pull requests and the 'compare changes' step takes 10 minutes! Create pull requests make the browser crashed!

Originally created by @MsBuggy on GitHub (Nov 3, 2017). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.2 windows-amd64 - Git version: 2.11.0 windows - Operating system: windows 2008 R2 _16 CPU cores and 16GB RAM_ - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: ## Description I try to create pull requests and the 'compare changes' step takes 10 minutes! Create pull requests make the browser crashed!
GiteaMirror commented 2025-11-02 03:52:20 -06:00
Author
Owner
Copy Link

@lflare commented on GitHub (Nov 3, 2017):

How big of a repository are we talking about here? Do you have any logs?

@lflare commented on GitHub (Nov 3, 2017): How big of a repository are we talking about here? Do you have any logs?
GiteaMirror commented 2025-11-02 03:52:20 -06:00
Author
Owner
Copy Link

@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 03:52:20 -06:00
Author
Owner
Copy Link

@adelowo commented on GitHub (Dec 2, 2018):

I am currently experiencing this too on a project with a size of 146MB. :)

@adelowo commented on GitHub (Dec 2, 2018): I am currently experiencing this too on a project with a size of `146MB`. :)
GiteaMirror commented 2025-11-02 03:52:21 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Dec 2, 2018):

@adelowo maybe you can send a pull request.

@lunny commented on GitHub (Dec 2, 2018): @adelowo maybe you can send a pull request.
GiteaMirror commented 2025-11-02 03:52:21 -06:00
Author
Owner
Copy Link

@adelowo commented on GitHub (Dec 2, 2018):

@lunny I will try to take a look at it in the coming week hopefully.

By the way, mine takes 3 -5 minutes without causing a browser crash

@adelowo commented on GitHub (Dec 2, 2018): @lunny I will try to take a look at it in the coming week hopefully. By the way, mine takes 3 -5 minutes without causing a browser crash
GiteaMirror commented 2025-11-02 03:52:21 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 31, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 31, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 03:52:21 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 6, 2019):

@MsBuggy @webjoel @adelowo is this still a problem?

@lunny commented on GitHub (Feb 6, 2019): @MsBuggy @webjoel @adelowo is this still a problem?
GiteaMirror commented 2025-11-02 03:52:21 -06:00
Author
Owner
Copy Link

@webjoel commented on GitHub (Feb 6, 2019):

@lunny I am using an old version (commit 1b2aff0), I have not yet been able to upgrade to the latest version, so I'm not sure if the problem persists in the new ones, but in this one I'm using the slowness continues.

@webjoel commented on GitHub (Feb 6, 2019): @lunny I am using an old version (commit 1b2aff0), I have not yet been able to upgrade to the latest version, so I'm not sure if the problem persists in the new ones, but in this one I'm using the slowness continues.
GiteaMirror commented 2025-11-02 03:52:22 -06:00
Author
Owner
Copy Link

@adelowo commented on GitHub (Feb 6, 2019):

@lunny I no longer have access to the repository so I will not be able to test that

@adelowo commented on GitHub (Feb 6, 2019): @lunny I no longer have access to the repository so I will not be able to test that
GiteaMirror commented 2025-11-02 03:52:22 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Feb 6, 2019):

Ok that Gitea version is before the substantial speed up pr #4921 @Typeless made was pulled.

@zeripath commented on GitHub (Feb 6, 2019): Ok that Gitea version is before the substantial speed up pr #4921 @Typeless made was pulled.
GiteaMirror commented 2025-11-02 03:52:22 -06:00
Author
Owner
Copy Link

@webjoel commented on GitHub (Feb 6, 2019):

@lunny @lafriks Is it possible for this PR ( #4921 ) to inner in 1.7.x release? Or is it only 1.8?

Anyway, for me can close this issue, since other related issues were also closed, so the best should have generated performance gain.

@webjoel commented on GitHub (Feb 6, 2019): @lunny @lafriks Is it possible for this PR ( #4921 ) to inner in 1.7.x release? Or is it only 1.8? Anyway, for me can close this issue, since other related issues were also closed, so the best should have generated performance gain.
GiteaMirror commented 2025-11-02 03:52:22 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Feb 6, 2019):

@webjoel only bug fixes are backported

@lafriks commented on GitHub (Feb 6, 2019): @webjoel only bug fixes are backported
GiteaMirror commented 2025-11-02 03:52:23 -06:00
Author
Owner
Copy Link

@1902sysad commented on GitHub (Aug 8, 2019):

im having this issue, is there any workarounds?

@1902sysad commented on GitHub (Aug 8, 2019): im having this issue, is there any workarounds?
GiteaMirror commented 2025-11-02 03:52:23 -06:00
Author
Owner
Copy Link

@typeless commented on GitHub (Aug 8, 2019):

I encountered this a couple of times. I tried to sample the timings with ps -u git -o cmd manually and got

CWD CMD
-   /volume1/homes/git/gitea/gitea web
-   /bin/git -c credential.helper= -c protocol.version=2 -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= remote add -f 1565248623376910366 /volume1/homes/git/gitea/repositories/saturn/large-repo.git
-   /var/packages/Git/target/libexec/git-core/git fetch 1565248623376910366
-   git-upload-pack /volume1/homes/git/gitea/repositories/saturn/large-repo.git
-   /var/packages/Git/target/libexec/git-core/git rev-list --objects --stdin --not --all --quiet

I guess git remote add -f is probably the one taking long time.

@typeless commented on GitHub (Aug 8, 2019): I encountered this a couple of times. I tried to sample the timings with `ps -u git -o cmd` manually and got ``` CWD CMD - /volume1/homes/git/gitea/gitea web - /bin/git -c credential.helper= -c protocol.version=2 -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= remote add -f 1565248623376910366 /volume1/homes/git/gitea/repositories/saturn/large-repo.git - /var/packages/Git/target/libexec/git-core/git fetch 1565248623376910366 - git-upload-pack /volume1/homes/git/gitea/repositories/saturn/large-repo.git - /var/packages/Git/target/libexec/git-core/git rev-list --objects --stdin --not --all --quiet ``` I guess `git remote add -f` is probably the one taking long time.
GiteaMirror commented 2025-11-02 03:52:23 -06:00
Author
Owner
Copy Link

@typeless commented on GitHub (Aug 8, 2019):

Looking into it further, that should be at 1608f63e39/modules/git/repo_compare.go (L55)

@typeless commented on GitHub (Aug 8, 2019): Looking into it further, that should be at https://github.com/go-gitea/gitea/blob/1608f63e396c78bcbea3605b812556ddf441a6c4/modules/git/repo_compare.go#L55
GiteaMirror commented 2025-11-02 03:52:23 -06:00
Author
Owner
Copy Link

@typeless commented on GitHub (Aug 8, 2019):

A quick workaround, I assume, is to decouple git remote add and git fetch.
And then make git fetch fetch only the branch in question, not all the other refs.

@typeless commented on GitHub (Aug 8, 2019): A quick workaround, I assume, is to decouple `git remote add` and `git fetch.` And then make `git fetch` fetch only the branch in question, not all the other refs.
GiteaMirror commented 2025-11-02 03:52:24 -06:00
Author
Owner
Copy Link

@typeless commented on GitHub (Aug 8, 2019):

@1902sysad Hey, if you know how to build Gitea from source, please try https://github.com/go-gitea/gitea/pull/7797/files to see if it fixes your problem.

@typeless commented on GitHub (Aug 8, 2019): @1902sysad Hey, if you know how to build Gitea from source, please try https://github.com/go-gitea/gitea/pull/7797/files to see if it fixes your problem.
GiteaMirror commented 2025-11-02 03:52:24 -06:00
Author
Owner
Copy Link

@1902sysad commented on GitHub (Aug 8, 2019):

Thank you we will be trying this soon

@1902sysad commented on GitHub (Aug 8, 2019): Thank you we will be trying this soon
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1204
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?