github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-09 04:25:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Docker instance always using CPU #7654

New Issue
Closed
opened 2025-11-02 07:32:34 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 07:32:34 -06:00
Owner
Copy Link

Originally created by @binarydad on GitHub (Aug 3, 2021).

  • Gitea version (or commit ref): 1.14.5
  • Operating system: Ubuntu 18 on latest Docker instance
  • Not sure the DB, whatever was installed with Docker
  • No logs seem out of place, besides standard HTTP requests

Description

The instance works fine, and doesn't seem sluggish, but I've noticed there is ALWAYS CPU activity. The Ubuntu host shows the gitea instance at around 4-6%. The docker container stats show it's higher, of course. Still, it's constant.

What is causing this constant CPU usage? Thanks.

Host process CPU:
image

Docker stats (Portainer):
image

Originally created by @binarydad on GitHub (Aug 3, 2021). <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq) 5. 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.14.5 - Operating system: Ubuntu 18 on latest Docker instance - Not sure the DB, whatever was installed with Docker - No logs seem out of place, besides standard HTTP requests ## Description The instance works fine, and doesn't seem sluggish, but I've noticed there is ALWAYS CPU activity. The Ubuntu host shows the `gitea` instance at around 4-6%. The docker container stats show it's higher, of course. Still, it's constant. What is causing this constant CPU usage? Thanks. Host process CPU: ![image](https://user-images.githubusercontent.com/1760607/128020806-300a4fe3-0fea-4e62-bae3-532f7e8de369.png) Docker stats (Portainer): ![image](https://user-images.githubusercontent.com/1760607/128020578-a18f103b-3bb0-478f-ba88-a685e30d3ad6.png)
GiteaMirror added the issue/duplicate label 2025-11-02 07:32:34 -06:00
GiteaMirror commented 2025-11-02 07:32:35 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Aug 3, 2021):

Please try 1.15.0-RC2.

@zeripath commented on GitHub (Aug 3, 2021): Please try 1.15.0-RC2.
GiteaMirror commented 2025-11-02 07:32:35 -06:00
Author
Owner
Copy Link

@binarydad commented on GitHub (Aug 3, 2021):

Please try 1.15.0-RC2.

Got it. I came across this (https://github.com/go-gitea/gitea/issues/15542) after posting, and noticed your comments about this change in 1.15. I'll just wait for the RTM. Thank you!

@binarydad commented on GitHub (Aug 3, 2021): > > > Please try 1.15.0-RC2. Got it. I came across this (https://github.com/go-gitea/gitea/issues/15542) after posting, and noticed your comments about this change in 1.15. I'll just wait for the RTM. Thank you!
GiteaMirror commented 2025-11-02 07:32:35 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Aug 3, 2021):

Why wait?

If no-one tests the RCs - they're not getting released.

@zeripath commented on GitHub (Aug 3, 2021): Why wait? If no-one tests the RCs - they're not getting released.
GiteaMirror commented 2025-11-02 07:32:36 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Aug 3, 2021):

Anyway I'll mark this as a duplicate of #15542

@zeripath commented on GitHub (Aug 3, 2021): Anyway I'll mark this as a duplicate of #15542
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 issue/duplicate
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#7654
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?