We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The panel currently shows 11GB of RAM usage, while in reality the server process only consumes 1.4GB
While docker stats shows
docker stats
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS <redacted> <redacted> 3.01% 1.467GiB / 19.47GiB 7.53% 542MB / 1.74GB 7.87GB / 1.52MB 28 <redacted> <redacted> 2.94% 651.8MiB / 8.041GiB 7.91% 240MB / 602MB 7.89GB / 1.47MB 26
And free -h shows
free -h
total used free shared buff/cache available Mem: 62G 3.5G 28G 258M 30G 58G Swap: 58G 1.0M 58G
Linux 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5+deb10u2 (2019-08-08) x86_64 GNU/Linux
$ sudo docker info Client: Debug Mode: false Server: Containers: 5 Running: 4 Paused: 0 Stopped: 1 Images: 7 Server Version: 19.03.1 Storage Driver: btrfs Build Version: Btrfs v4.7.3 Library Version: 101 Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: 894b81a4b802e4eb2a91d1ce216b8817763c29fb runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f init version: fec3683 Security Options: apparmor seccomp Profile: default Kernel Version: 4.19.0-5-amd64 Operating System: Debian GNU/Linux 10 (buster) OSType: linux Architecture: x86_64 CPUs: 8 Total Memory: 62.79GiB Name: <redacted> ID: <redacted> Docker Root Dir: /var/lib/docker Debug Mode: false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false WARNING: No swap limit support
To Reproduce
echo 1 > /proc/sys/vm/drop_caches
Expected behavior Panel to show actual process RAM usage and not RAM used for caching purposes by the Linux kernel.
The text was updated successfully, but these errors were encountered:
Duplicate of #1356 maybe
Sorry, something went wrong.
I've gone ahead and edited the issue with my new findings.
This is likely being caused by incorrect math in the old daemon, the new one uses the same logic Docker uses to calculate usage:
https://github.com/pterodactyl/wings/blob/develop/server/resources.go
Closing, fixed in wings.
Successfully merging a pull request may close this issue.
Background
Describe the bug
The panel currently shows 11GB of RAM usage, while in reality the server process only consumes 1.4GB
While
docker stats
showsAnd
free -h
showsLinux 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5+deb10u2 (2019-08-08) x86_64 GNU/Linux
To Reproduce
echo 1 > /proc/sys/vm/drop_caches
from the docker hostExpected behavior
Panel to show actual process RAM usage and not RAM used for caching purposes by the Linux kernel.
The text was updated successfully, but these errors were encountered: