Inconsistent System Status in Gitea Admin Panel

[H0llyW00dzZ]

Description

It seems there is an overflow issue with the Memory Usage in the System Status.

Gitea Version

1.23.1

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

Sessions are using files for read/write operations through the disk, not memory:

However, this is the accurate memory usage as viewed on Grafana:

Git Version

2.47.1

Operating System

Linux

How are you running Gitea?

Running on Kubernetes in Deployment mode (not StatefulSet), using Vertical Pod Autoscaler (VPA) for scaling memory and CPU.

Database

SQLite

[H0llyW00dzZ]

The output from kubectl also matches what is shown on Grafana.

h0llyw00dzz@ubuntu-pro:~$ kubectl top pods -n gitea
NAME                     CPU(cores)   MEMORY(bytes)   
gitea-x-x                1105m        4634Mi 

[wxiaoguang]

It seems there is an overflow issue with the Memory Usage in the System Status.

That page is just for fun, not useful and no need to seriously treat it (I never use that page)

---

The reported Memory Usage is from Golang runtime, if you'd like to figure out why there is difference, you need to look into how OS or Golang runtime works.

[H0llyW00dzZ]

It seems there is an overflow issue with the Memory Usage in the System Status.

That page is just for fun, not useful and no need to seriously treat it (I never use that page)

The reported Memory Usage is from Golang runtime, if you'd like to figure out why there is difference, you need to look into how OS or Golang runtime works.

Oh, I also have a question about the [session] configuration. When it is set to file, does it read/write directly to the disk rather than using memory first?

[wxiaoguang]

Oh, I also have a question about the [session] configuration. When it is set to file, does it read/write directly to the disk rather than using memory first?

IIRC: it reads/writes directly to the disk

[H0llyW00dzZ]

Oh, I also have a question about the [session] configuration. When it is set to file, does it read/write directly to the disk rather than using memory first?

IIRC: it reads/writes directly to the disk

Alright, then it's stable to run Gitea on Kubernetes without a database like MySQL or PostgreSQL, as it uses SQLite, which read/writes directly to disk. Sessions are stored in files, not memory, by attaching external storage (PVC) with a premium disk. Redis is used only for caching because my Gitea deployment on Kubernetes is simple, not complex, and doesn't require a StatefulSet.