Everything posted by casperse
-
HDD Auto spinup on Plex container activity
Hmm yes I do have allot of things running on the server! But I did manage to get individual Sleep of drives working by having separate UAD for download and other things (There is a nice FAQ about this setup in the forum) - and things I don't want to have on the array And yes I have allot of apps running 24/7 I think the cache is the problem! Plex and all appdata is located on the CACHE drive NVME drive and its the same drive that is used as cache creating the high I/O? So I cant use Plex %CPU because everything is on my cache drive - But I still experience "slow" playback from Plex at strange hours because the other disk is in sleep state - I would need to find another trigger, to bad you cant set Plex user web activity = Spin-up 🙂
-
Video Preloader (avoids HDD spinup latency when starting a Movie or Episode through Plex, Jellyfin or Emby)
Version 0.8 did something with the srt files it keeps adding srt files forever - without any TV show clip, maybee the size is under the limit?
-
Video Preloader (avoids HDD spinup latency when starting a Movie or Episode through Plex, Jellyfin or Emby)
Hi mgutt Just wanted to let you know that I just tried your script, and I think its working 100% Logfile: Preload /mnt/user/movies/Movies/Friends with Kids (2012)/Friends with Kids (2012) [Bluray.720p.x264.8Bit.DTS.5.1].mkv (6.835s) Preload /mnt/user/movies/Movies/Transylvania 6-5000 (1985)/Transylvania 6-5000 (1985) [Bluray.720p.x264.8Bit.DTS.2.0].mkv (0.337s) Script Starting Oct 21, 2020 20:20.51 Full logs for this script are available at /tmp/user.scripts/tmpScripts/Plex Preloader v0.7/log.txt Script Finished Oct 21, 2020 20:20.51 Update: Did a test added "TV Shows" and I could see srt files being loaded (Running Unraid 6.8.3) So how to get 1TB of memory!!! LOL Great work, you have really made a big impact on my Plex server!
-
HDD Auto spinup on Plex container activity
I use the Plex inc Docker moved away from the other ones, maybe it's different? Had it running across all tree trying to catch it
-
HDD Auto spinup on Plex container activity
-
HDD Auto spinup on Plex container activity
So I did run both script at the same time: But below I don't see the CPU go above 1% Not a single time! This is really strange
-
rsync Incremental Backup
You got me thinking about the missing DB backup of the Plex Appdata folder being very large on the NVme So I wanted to use your incremental backup script, but I am not sure if I need to remove the cache in the path and also not sure if this supports UAD for drives. I am trying to create the backup on a drive not the Array Like this: # settings user_share="/appdata/plex" backup_share="/mnt/disks/Drive1/backup" days=14 # preserve backups of the last X days months=12 # preserve backups of the first day of the last X month years=3 # preserve backups of the first january of the last X years fails=3 # preserve the recent X failed backups ..... But cache path fails (Got it working with normal path) Update this will create a backup on my UAD disk with path: \Drive1\backup\appdata\plex\.20201021_144056 But I am having a little problem using the cache path, I tried to replace all the /mnt/user/ in the script but keep getting errors Is it better just to use the /mnt/user and not the cache direct for the script to work? (You got me using /cache/ every now! 🙂 )
-
HDD Auto spinup on Plex container activity
Hi @mgutt This is another great idea you have! I think mostly my drives doesn't spin down before evening, but I have had complains late at night that the stream did not start - and then you had to press play again? (Spin-up) (Not the end of the world but if I can fix it...then why not ) So running this on Plex I get these spikes? I checked and I have no TV-recording, no playback, and no scanning of library What do you think could be causing these spikes? Highest value was 45.97 From Plex
-
Memory usage very HIGH? [Solved]
Thanks for all this information I have to read more to grasp it all Not sure how you write directly to cache from a windows PC... (For Nextcloud I just added the path as cache to the docker temp folder) If I go to my \\IP\cache\temp I can't connect to it - do you have to modify the SMB config in order to make your cache drive directly accessible?
-
Memory usage very HIGH? [Solved]
Sorry for the delay replying you! I found that no matter what path I write in Emby it will create a subdir in the tmp/ram dir as "transcoding-temp" I deleted this and used your script to create a EmbyRamScratch that it can create the "transcoding-temp" under So far no problems after this change! works great! Thanks I also added this to my docker setting running Krusader looks ok now! Sorry I have updated my "warning" in the topic for tweaks that I created - The changes have made the biggest speed improvement to my setup so far! No the docker.img have just always been on the cache (Just not used the cache in the path, only the prefer on cache setting before) Sure thing this really utilize the NVMe (Only drawback is that I had to upgrade it to a Samsung MZ-V7S2T0BW 970 Evo Plus [2 TB] $$$ and my limit in PCIe slots I can only have 1 NVMe) Done! and thanks! As stated before Emby creates a "transcoding-temp" dir (Must be hardcoded) but I have pointed that to the new "EmbyRamScratch/trancoding-temp/" No only one NVMe and so far this is okay. I have around 8-900G for cache a day and rest for VM/Docker/Appdata/docker.img Yes I have the excellent community tools that creates backup of the VM's/Appdata/docker.img I have excluded the 800G Plex appdata folder, have a old yearly backup - and worst case is just that it needs to do a rescan of the library Again thanks for all your help! much appreciated! 🙏 BTW: I have created a local shared temp that I have as prefer on cache. So if I want to have something permanently on the cache drive I can put it there also used for special files on NeXTcloud that requires fast access and transfer speeds 🙂Would it also be good to change path to /cache/ here?
-
Memory usage very HIGH? [Solved]
Can I just delete this? No idea where its from? Deleting these old transcode folders (Shouldnt they be delete automatically?) Update looks like this is from Emby: After deleting this folder, and pointing EMBY transcode to the same "PlexRamscratch" I now get: du -sh /tmp 183M /tmp And my memory is now: down to normal JAHUU! I don't know enough about this, but isn't memory temporary and turning your PC of should flush the tmp right?
-
Memory usage very HIGH? [Solved]
du -h --max-depth=3 /tmp 0 /tmp/mc-root 0 /tmp/PlexRamScratch/Transcode/Detection 0 /tmp/PlexRamScratch/Transcode/Sessions 0 /tmp/PlexRamScratch/Transcode 0 /tmp/PlexRamScratch 0 /tmp/CA_logs 0 /tmp/Transcode/Detection 0 /tmp/Transcode/Sessions 0 /tmp/Transcode 20G /tmp/transcoding-temp <-------------------------------- Dont know why this is here? 8.0K /tmp/user.scripts/tmpScripts/PlexRamScratch 8.0K /tmp/user.scripts/tmpScripts 0 /tmp/user.scripts/running 4.0K /tmp/user.scripts/finished 20K /tmp/user.scripts 7.0M /tmp/fix.common.problems 0 /tmp/ca_notices 4.0K /tmp/emhttp 0 /tmp/unassigned.devices/scripts 16K /tmp/unassigned.devices/config 28K /tmp/unassigned.devices 16K /tmp/recycle.bin 0 /tmp/community.applications/tempFiles/templates-community-apps 7.9M /tmp/community.applications/tempFiles 7.9M /tmp/community.applications 0 /tmp/ca.backup2/tempFiles 0 /tmp/ca.backup2 4.0K /tmp/nvidia 0 /tmp/.X11-unix 0 /tmp/.ICE-unix 536K /tmp/plugins 20G /tmp The " /tmp/transcoding-temp" might be Emby? can I remove this folder from RAM (Emby is just for test and no one is using this server) I use the Plex container from Plexinc so far this has worked best for me (Have tried them all) Don't know did the Krusader install from a spaceinvader video long time ago? Docker: Plex: I didn't think I needed to change this to cache, but I guess that would be best since I have all 800G in my cache NVMe So I will change this now: (I just changed this for Emby also, using the same transcoding dir in RAM)
-
Memory usage very HIGH? [Solved]
I went back and enabled the cache path for the docker.img :-) Only activity I can see is Plex scanning libraries - no transcoding So the CPU could be indexing and preview thumbnails? But memory is back to 99%-100% du -sh /tmp 20G /tmp df -h -t tmpfs Filesystem Size Used Avail Use% Mounted on tmpfs 32M 632K 32M 2% /run tmpfs 32G 8.0K 32G 1% /dev/shm cgroup_root 8.0M 0 8.0M 0% /sys/fs/cgroup tmpfs 128M 1.9M 127M 2% /var/log tmpfs 1.0M 0 1.0M 0% /mnt/disks tmpfs 8.0G 0 8.0G 0% /tmp/PlexRamScratch (Yes I did set the PlexRamScratch to 8G just to be sure.... like you did I have a P2000 doing the trancodes and I don't want the RAM to be a bottleneck) ps aux | awk '{print $6/1024 " MB\t\t" $11}' | sort -n 0.00390625 MB sh 0.0546875 MB /usr/sbin/crond 0.0546875 MB /usr/sbin/crond 0.0625 MB /bin/sh 0.0625 MB /bin/sh 0.0625 MB curl 0.0664062 MB /bin/sh 0.0664062 MB /bin/sh 0.0703125 MB /bin/sh 0.0703125 MB /bin/sh 0.0703125 MB /bin/sh 0.0703125 MB /bin/sh 0.0703125 MB /bin/sh 0.0703125 MB xargs 0.0742188 MB /usr/bin/tini 0.0820312 MB /bin/sh 0.0820312 MB /usr/bin/tini 0.0820312 MB /usr/bin/tini 0.0820312 MB sleep 0.0859375 MB /bin/sh 0.0859375 MB /bin/sh 0.0859375 MB grep 0.09375 MB /bin/sh 0.09375 MB /bin/sh 0.09375 MB /bin/sh 0.09375 MB /bin/sh 0.09375 MB /bin/sh 0.09375 MB /bin/sh 0.09375 MB /usr/sbin/acpid 0.0976562 MB /bin/sh 0.101562 MB /bin/sh 0.101562 MB /usr/sbin/wsdd 0.105469 MB /bin/sh 0.109375 MB /bin/sh 0.109375 MB /usr/sbin/avahi-dnsconfd 0.117188 MB /bin/sh 0.152344 MB php7 0.15625 MB /bin/sh 0.167969 MB dbus-run-session 0.167969 MB logger 0.171875 MB pgrep 0.191406 MB curl 0.195312 MB bash 0.253906 MB bash 0.257812 MB grep 0.257812 MB grep 0.261719 MB avahi-daemon: 0.277344 MB /usr/sbin/crond 0.320312 MB /usr/bin/dbus-daemon 0.320312 MB xcompmgr 0.339844 MB dbus-daemon 0.339844 MB drill 0.417969 MB curl 0.417969 MB curl 0.417969 MB curl 0.425781 MB curl 0.457031 MB curl 0.457031 MB curl 0.46875 MB /bin/bash 0.46875 MB /bin/bash 0.492188 MB /bin/bash 0.492188 MB /bin/bash 0.496094 MB curl 0.53125 MB /usr/bin/privoxy 0.570312 MB /bin/bash 0.585938 MB /bin/bash 0.59375 MB /bin/bash 0.644531 MB /bin/bash 0.730469 MB /bin/timeout 0.734375 MB /bin/timeout 0.734375 MB /bin/timeout 0.734375 MB /bin/timeout 0.738281 MB /bin/timeout 0.738281 MB sleep 0.742188 MB sleep 0.753906 MB /usr/local/sbin/shfs 0.757812 MB Plex 0.792969 MB /bin/timeout 0.792969 MB /bin/timeout 0.792969 MB /bin/timeout 0.796875 MB /bin/timeout 0.800781 MB /bin/timeout 0.800781 MB /bin/timeout 0.824219 MB nginx: 0.851562 MB curl 0.851562 MB curl 0.851562 MB curl 0.855469 MB curl 0.910156 MB curl 0.945312 MB curl 0.980469 MB nginx: 0.980469 MB nginx: 0.980469 MB nginx: 1 MB find 1.01562 MB nginx: 1.17969 MB /usr/bin/privoxy 1.1875 MB nginx: 1.32031 MB nginx: 1.32812 MB /usr/bin/openvpn 1.33594 MB /usr/bin/openvpn 1.39453 MB nginx: 1.40234 MB nginx: 1.40625 MB /usr/bin/docker-proxy 1.40625 MB /usr/bin/docker-proxy 1.40625 MB /usr/bin/docker-proxy 1.40625 MB /usr/bin/docker-proxy 1.41016 MB /usr/bin/docker-proxy 1.41016 MB /usr/bin/docker-proxy 1.41016 MB /usr/bin/docker-proxy 1.41016 MB /usr/bin/docker-proxy 1.41016 MB /usr/bin/docker-proxy 1.41016 MB /usr/bin/docker-proxy 1.46875 MB /usr/sbin/atd 1.50781 MB nginx: 1.55078 MB /usr/sbin/inetd 1.64453 MB init 1.67578 MB /sbin/agetty 1.69531 MB /sbin/agetty 1.71875 MB /usr/lib/plexmediaserver/Plex 1.74219 MB /sbin/agetty 1.76562 MB sort 1.77734 MB /sbin/agetty 1.78125 MB /sbin/agetty 1.78516 MB /sbin/agetty 1.79297 MB /usr/sbin/crond 2.01562 MB /sbin/rpcbind 2.01562 MB kdeinit5: 2.07812 MB /usr/bin/dbus-daemon 2.17578 MB /usr/sbin/rpc.mountd 2.28125 MB find 2.29297 MB /usr/sbin/rsyslogd 2.30078 MB /usr/bin/docker-proxy 2.32031 MB /bin/bash 2.32422 MB ps 2.36328 MB /usr/bin/docker-proxy 2.36328 MB /usr/bin/docker-proxy 2.36719 MB find 2.37109 MB /usr/bin/docker-proxy 2.37109 MB /usr/bin/docker-proxy 2.39062 MB find 2.39453 MB /bin/bash 2.40625 MB find 2.42578 MB /usr/bin/docker-proxy 2.51562 MB find 2.54688 MB find 2.57422 MB find 2.57812 MB /bin/bash 2.57812 MB /bin/bash 2.59766 MB /usr/sbin/sshd 2.62891 MB find 2.63672 MB /bin/bash 2.63672 MB find 2.64062 MB /bin/bash 2.64062 MB /bin/bash 2.64062 MB /bin/bash 2.64062 MB /bin/bash 2.64062 MB /bin/bash 2.64062 MB /bin/bash 2.64062 MB /bin/bash 2.64062 MB /bin/bash 2.79297 MB /bin/bash 2.84375 MB /usr/lib/kf5/klauncher 2.89062 MB awk 2.92969 MB find 3.02344 MB /usr/bin/tint2 3.08594 MB php-fpm: 3.24219 MB /bin/bash 3.57812 MB avahi-daemon: 3.71875 MB /usr/bin/docker-proxy 3.72266 MB nginx: 3.74219 MB /usr/bin/docker-proxy 3.76562 MB /usr/bin/docker-proxy 3.76562 MB /usr/bin/docker-proxy 3.77344 MB /usr/bin/docker-proxy 3.78906 MB /usr/bin/docker-proxy 3.80469 MB /usr/bin/docker-proxy 3.83594 MB /usr/bin/docker-proxy 3.84375 MB /usr/bin/docker-proxy 3.87891 MB /usr/bin/docker-proxy 3.90625 MB /usr/sbin/virtlockd 3.92188 MB /usr/bin/docker-proxy 3.97266 MB /sbin/udevd 4.01953 MB -bash 4.08203 MB /usr/local/sbin/emhttpd 4.26562 MB /usr/bin/docker-proxy 4.30469 MB /usr/bin/openbox 4.61719 MB /usr/bin/docker-proxy 4.77344 MB /usr/bin/docker-proxy 4.78125 MB /app/unpackerr 4.85156 MB /usr/sbin/ntpd 5.16797 MB ttyd 5.66797 MB /sbin/rpc.statd 5.98047 MB containerd-shim 5.99219 MB /bitwarden_rs 6.04688 MB containerd-shim 6.05859 MB nginx: 6.09766 MB containerd-shim 6.10547 MB /sbin/haveged 6.19922 MB containerd-shim 6.21094 MB containerd-shim 6.23438 MB containerd-shim 6.30859 MB containerd-shim 6.36328 MB containerd-shim 6.44141 MB nginx: 6.44922 MB containerd-shim 6.44922 MB nginx: 6.45312 MB nginx: 6.46094 MB containerd-shim 6.50781 MB containerd-shim 6.5625 MB containerd-shim 6.62109 MB containerd-shim 6.62109 MB containerd-shim 6.88672 MB nginx: 6.98828 MB nginx: 7.03125 MB /usr/sbin/nmbd 7.28516 MB php-fpm: 7.29297 MB /usr/sbin/smbd 7.42578 MB containerd-shim 7.52734 MB /usr/sbin/virtlogd 7.86719 MB php-fpm: 7.86719 MB php-fpm: 8.125 MB /usr/sbin/smbd 8.22656 MB containerd-shim 8.42578 MB containerd-shim 8.43359 MB containerd-shim 8.4375 MB /usr/bin/slim 8.79297 MB containerd-shim 8.83594 MB containerd-shim 8.96094 MB containerd-shim 8.98828 MB nginx: 9.08203 MB containerd-shim 9.74609 MB containerd-shim 9.79297 MB /usr/sbin/winbindd 9.89062 MB php-fpm: 10.1094 MB php-fpm: 10.3555 MB /usr/bin/python3 10.9336 MB /usr/sbin/winbindd 11.3438 MB php-fpm: 12.2266 MB /usr/local/emhttp/plugins/unbalance/unbalance 12.5273 MB /usr/sbin/winbindd 13.0664 MB php-fpm: 13.0664 MB php-fpm: 13.0742 MB php-fpm: 13.3711 MB php-fpm: 13.4844 MB php-fpm: 13.5625 MB php-fpm: 13.5625 MB php-fpm: 13.5977 MB /usr/local/emhttp/plugins/controlr/controlr 14.6719 MB /usr/bin/python 14.7695 MB php-fpm: 14.8789 MB /usr/bin/python 14.9844 MB /usr/bin/python 15.0859 MB /usr/sbin/smbd 15.1484 MB /usr/sbin/smbd 15.1992 MB /usr/sbin/smbd 17.4922 MB /usr/bin/python 17.9062 MB /usr/sbin/smbd 20.4023 MB /usr/lib/plexmediaserver/Plex 20.6523 MB /usr/sbin/smbd 21.168 MB /usr/bin/python 22.4844 MB /usr/sbin/libvirtd 25.3398 MB Plex 26.5938 MB python 34.2461 MB /usr/libexec/Xorg 34.8789 MB Plex 35.5273 MB docker 37.1523 MB Plex 37.3242 MB Plex 37.9258 MB containerd 38.168 MB /usr/bin/python 39.0625 MB deluge-web 40.3359 MB php7 43.6914 MB php-fpm: 43.8945 MB php-fpm: 45.5078 MB php-fpm: 51.5078 MB /usr/sbin/python3 52.168 MB /usr/sbin/Xvnc 54.707 MB python3 64.25 MB Plex 79.7578 MB /usr/bin/dockerd 104.973 MB python3 110.766 MB /app/radarr/bin/Radarr 136.883 MB /usr/local/sbin/shfs 141.602 MB /app/Jackett/jackett 144.734 MB /opt/ombi/Ombi 146.723 MB mono 167.867 MB /app/radarr/bin/Radarr 188.879 MB mono 280.812 MB mono 293.574 MB system/EmbyServer 332.719 MB /usr/sbin/mysqld 359.27 MB java 788.543 MB rslsync 914.41 MB /usr/lib/plexmediaserver/Plex 2107.17 MB /usr/bin/qemu-system-x86_64 3276.16 MB /usr/bin/qemu-system-x86_64 4268.11 MB /usr/bin/qemu-system-x86_64 4302 MB /usr/bin/qemu-system-x86_64 5088.28 MB krusader 16605.5 MB /usr/bin/qemu-system-x86_64 Again thanks for your help! much appreciated
-
Memory usage very HIGH? [Solved]
I have created the script in the "User Scripts" and updated the path (Thanks!) its working Only thing I can't figure out is if I have to enable schedule for this script here? UPDATE: Excellent guide thanks all is running now!
-
Memory usage very HIGH? [Solved]
I used this guide when I first created my Plex server to use my RAM for transcoding: Guess things have evolved since then UPDATE: Did the script and its working One question should I schedule this to run in the User Scripts?
-
Memory usage very HIGH? [Solved]
I don't get the error anymore but Memory is going up ..... 0.00390625 MB sh 0.0507812 MB /usr/sbin/crond 0.0664062 MB /bin/sh 0.0664062 MB /bin/sh 0.0664062 MB /usr/bin/tini 0.09375 MB /usr/sbin/acpid 0.101562 MB /usr/sbin/wsdd 0.109375 MB /usr/sbin/avahi-dnsconfd 0.167969 MB dbus-run-session 0.167969 MB logger 0.214844 MB /usr/sbin/crond 0.261719 MB avahi-daemon: 0.289062 MB xcompmgr 0.296875 MB dbus-daemon 0.300781 MB /bin/sh 0.316406 MB /usr/bin/dbus-daemon 0.347656 MB /usr/bin/tini 0.359375 MB bash 0.367188 MB bash 0.449219 MB /usr/sbin/crond 0.464844 MB /bin/bash 0.464844 MB /usr/bin/tini 0.5625 MB /bin/bash 0.679688 MB sleep 0.695312 MB sleep 0.710938 MB sleep 0.714844 MB sleep 0.726562 MB /usr/local/sbin/shfs 0.734375 MB /bin/timeout 0.738281 MB sleep 0.753906 MB sleep 0.984375 MB nginx: 0.984375 MB nginx: 0.984375 MB nginx: 1.01953 MB nginx: 1.1875 MB nginx: 1.21875 MB /usr/bin/privoxy 1.32812 MB /usr/bin/openvpn 1.39453 MB nginx: 1.39453 MB nginx: 1.39453 MB nginx: 1.46875 MB /usr/sbin/atd 1.53906 MB /bin/bash 1.55078 MB /usr/sbin/inetd 1.64453 MB init 1.67578 MB /sbin/agetty 1.69531 MB /sbin/agetty 1.74219 MB /sbin/agetty 1.77734 MB /sbin/agetty 1.78125 MB /sbin/agetty 1.78516 MB /sbin/agetty 1.78906 MB sort 1.79297 MB /usr/sbin/crond 2.01562 MB /sbin/rpcbind 2.03906 MB /bin/bash 2.04297 MB /bin/bash 2.07812 MB /usr/bin/dbus-daemon 2.14844 MB nginx: 2.15234 MB nginx: 2.17578 MB /usr/sbin/rpc.mountd 2.19141 MB /bin/bash 2.24609 MB /usr/lib/plexmediaserver/Plex 2.26562 MB /bin/bash 2.29297 MB /usr/sbin/rsyslogd 2.36328 MB /bin/bash 2.42188 MB /usr/bin/privoxy 2.42578 MB ps 2.51172 MB /bin/bash 2.59766 MB /usr/sbin/sshd 2.60156 MB /usr/bin/openvpn 2.80469 MB /bin/bash 2.84766 MB /usr/bin/tint2 2.89453 MB /bin/bash 2.93359 MB find 3.05469 MB awk 3.39844 MB /bin/bash 3.57812 MB avahi-daemon: 3.72266 MB nginx: 3.73438 MB /usr/bin/docker-proxy 3.73438 MB /usr/bin/docker-proxy 3.73438 MB /usr/bin/docker-proxy 3.73438 MB /usr/bin/docker-proxy 3.76953 MB /usr/bin/openbox 3.77344 MB /usr/bin/docker-proxy 3.80469 MB /usr/bin/docker-proxy 3.80469 MB /usr/bin/docker-proxy 3.80469 MB /usr/bin/docker-proxy 3.80469 MB /usr/bin/docker-proxy 3.83594 MB /usr/bin/docker-proxy 3.83594 MB /usr/bin/docker-proxy 3.83594 MB /usr/bin/docker-proxy 3.84375 MB /usr/bin/docker-proxy 3.85156 MB /usr/bin/docker-proxy 3.85156 MB /usr/bin/docker-proxy 3.85938 MB /usr/bin/docker-proxy 3.85938 MB /usr/bin/docker-proxy 3.86719 MB /usr/bin/docker-proxy 3.89062 MB /usr/bin/docker-proxy 3.89062 MB /usr/bin/docker-proxy 3.89062 MB /usr/bin/docker-proxy 3.96094 MB /usr/bin/docker-proxy 3.97266 MB /sbin/udevd 3.98828 MB /usr/bin/docker-proxy 3.98828 MB /usr/sbin/virtlockd 4.01953 MB -bash 4.07812 MB /usr/local/sbin/emhttpd 4.08594 MB /usr/bin/docker-proxy 4.08984 MB /usr/bin/docker-proxy 4.21875 MB /usr/bin/docker-proxy 4.29688 MB /usr/bin/docker-proxy 4.85156 MB /usr/sbin/ntpd 4.89844 MB /bitwarden_rs 4.98438 MB /usr/bin/docker-proxy 5.10938 MB php-fpm: 5.16016 MB ttyd 5.66797 MB /sbin/rpc.statd 5.91797 MB /usr/bin/docker-proxy 5.98047 MB nginx: 6.10547 MB /sbin/haveged 6.19531 MB /usr/bin/docker-proxy 6.24609 MB nginx: 6.24609 MB nginx: 6.24609 MB nginx: 6.90625 MB /usr/sbin/nmbd 7.23047 MB /usr/sbin/virtlogd 7.28125 MB /usr/sbin/smbd 7.51953 MB php-fpm: 7.90234 MB php-fpm: 8.04297 MB nginx: 8.08203 MB /usr/sbin/smbd 8.08203 MB nginx: 8.4375 MB /usr/bin/slim 8.93359 MB containerd-shim 8.96484 MB containerd-shim 8.98828 MB nginx: 9.29297 MB containerd-shim 9.30859 MB containerd-shim 9.34766 MB /usr/local/emhttp/plugins/unbalance/unbalance 9.38281 MB containerd-shim 9.39844 MB containerd-shim 9.4375 MB containerd-shim 9.48047 MB containerd-shim 9.48828 MB containerd-shim 9.51953 MB containerd-shim 9.51953 MB containerd-shim 9.51953 MB containerd-shim 9.53516 MB containerd-shim 9.54297 MB containerd-shim 9.57812 MB containerd-shim 9.58594 MB containerd-shim 9.61328 MB containerd-shim 9.61719 MB containerd-shim 9.66406 MB containerd-shim 9.82031 MB containerd-shim 9.92969 MB /usr/bin/python3 9.96484 MB /usr/sbin/winbindd 10.7812 MB php-fpm: 10.8203 MB /usr/sbin/winbindd 11.0234 MB /app/unpackerr 11.3438 MB php-fpm: 11.5898 MB containerd-shim 11.7188 MB containerd-shim 11.793 MB containerd-shim 11.9727 MB php-fpm: 12.3555 MB /usr/sbin/winbindd 12.7773 MB php-fpm: 12.8008 MB php-fpm: 13.3047 MB php-fpm: 13.418 MB /usr/local/emhttp/plugins/controlr/controlr 13.4375 MB php-fpm: 13.4375 MB php-fpm: 13.5039 MB php-fpm: 13.5039 MB php-fpm: 13.8086 MB php-fpm: 14.9961 MB /usr/sbin/smbd 15.0273 MB /usr/sbin/smbd 15.418 MB /usr/bin/python 16.5586 MB /usr/bin/python 16.6602 MB /usr/bin/python 17.1328 MB /usr/sbin/smbd 17.6523 MB /usr/bin/python 21.6797 MB /usr/sbin/smbd 22.8477 MB /usr/sbin/libvirtd 26.3164 MB python 26.4609 MB Plex 34 MB docker 34.2461 MB /usr/libexec/Xorg 35.1953 MB /usr/sbin/Xvnc 36.5742 MB krusader 38.4258 MB Plex 39.2656 MB /usr/bin/python 39.6094 MB containerd 39.6484 MB php-fpm: 39.7539 MB php-fpm: 39.9492 MB php-fpm: 41.4102 MB deluge-web 43.1602 MB Plex 51.0469 MB /usr/sbin/python3 54.082 MB python3 69.332 MB python3 81.8398 MB /usr/bin/dockerd 138.496 MB /app/radarr/bin/Radarr 146.586 MB /usr/local/sbin/shfs 158.039 MB /opt/ombi/Ombi 166.699 MB /usr/lib/plexmediaserver/Plex 167.602 MB /app/Jackett/jackett 178.035 MB /app/radarr/bin/Radarr 192.16 MB mono 197.223 MB mono 230.992 MB rslsync 291.141 MB mono 329.223 MB system/EmbyServer 331.602 MB /usr/sbin/mysqld 350.137 MB java 2120.78 MB /usr/bin/qemu-system-x86_64 3245.57 MB /usr/bin/qemu-system-x86_64 4245.45 MB /usr/bin/qemu-system-x86_64 4271.35 MB /usr/bin/qemu-system-x86_64 16604 MB /usr/bin/qemu-system-x86_64 The last 5 is the VM's with a total of 30 Gigs is there anything else above docker weise that stands out? (I was surprised that Emby uses so much and that Plex have so many different processes)
-
Memory usage very HIGH? [Solved]
Thanks! much appreciated! - I will try this next time I try the "cache" path again. (Yes I transcode to RAM but this was not the issue! - I had no trancodes and I even tried stopping PLEX)
-
Unraid tweaks for Media server performance?
I can just say that changing it back from cache to user my memory dropped and I have rebooted my servers more than 10 times and this is the only change? Could it be because I have a plex appdata that is near 800G?
-
Unraid tweaks for Media server performance?
UPDATE: This works! - My high memory usage was related to the encoding to RAM and thanks to @mgutt this is not a problem anymore! Actually I have never seen such speed scrolling through covers like I have now, both for Plex and Emby (I will make a post about this just to share my experience running both Emby and Plex in this thread soon) Again! thank you so much @mgutt your tweak really helped me allot - And also the trouble shooting here:
-
Memory usage very HIGH? [Solved]
UPDATE Found the problem - I can now run all the VM I have without getting above error after changing this back to "normal" This was caused by changing the docker to cache instead of user. This used a lot of memory:
-
Memory usage very HIGH? [Solved]
Yes I Agree, but having: My VM's 2 x Windows 10 = 3072 + 6144 MB = 9G 1 x pfSense = 3072 MB = 3G 1 x Hassio = 2048 MB = 2G 1 x Xpenology = 16384 MB = 16G (I found that I need to keep allocation = The orig. HW) A Total of: 30G - out of a total of 64G? I can't even start the last WIN 10 with 3G now without getting the : Shouldn't this be possible and then letting the host to use the last 34 Gigs ? What is the recommended memory value for a windows 10 for office work?
-
Memory usage very HIGH? [Solved]
-
Memory usage very HIGH? [Solved]
Hi All I have 64 Gigs of RAM (Useable 62.8 GiB) I have multiple Dockers (Not been a issue before adding new VM's) My VM's 2 x Windows 10 = 6144 MB = 12G 1 x pfSense = 3072 MB = 3G 1 x Hassio = 2048 MB = 2G 1 x Xpenology = 8192 MB = 8G Total: 25G Docker 38% of 62.8G = 24G Left = 13G The Load: TOP: Do I just need more RAM? (This system have a max of 64G 😞 ) Any tips to where I can cut memory usage? I got the CPU usage down by selecting different cores for each system As always your insight and expertise is much appreciated!
-
Unraid tweaks for Media server performance?
Hi thanks for the Tips! I have always had both Docker and Appdata on the same Nvme and because of the size I had to upgrade to a 2TB 😞 I just can't see any difference in the loading time of the posters etc... Between the above and the default This could be because I always had everything on the NVme? Is there any down size of keeping the changes using cache path?
-
Xpenology VM any one running this ?
Finally got the update working also on the 3617x - You need to run this script in order to do the latest DSM updates: https://xpenology.com/forum/topic/28183-running-623-on-esxi-synoboot-is-broken-fix-available/ However, if Jun's script is re-run after the system is fully started, everything is as it should be. So extracting the script from the loader, and adding it to post-boot actions appears to be a solution to this problem: Download the attached FixSynoboot.sh script (if you cannot see it attached to this post, be sure you are logged in) Copy the file to /usr/local/etc/rc.d chmod 0755 /usr/local/etc/rc.d/FixSynoboot.sh Thus, Jun's own code will re-run after the initial boot after whatever system initialization parameters that break the first run of the script no longer apply. This solution works with either 1.03b or 1.04b and is simple to install. This should be considered required for a virtual system running 6.2.3, and it won't hurt anything if installed or ported to another environment. 1) Check file is in temp dir ls /volume1/Temp/FixSynoboot.sh sudo -i cp /volume1/Temp/FixSynoboot.sh /usr/local/etc/rc.d chmod 0755 /usr/local/etc/rc.d/FixSynoboot.sh ls -la /usr/local/etc/rc.d/FixSynoboot.sh -rwxr-xr-x 1 root root 2184 May 18 17:54 FixSynoboot.sh Ensure the file configuration is correct, reboot the nas and FixSynoboot will be enabled. That's it I am now running: I even did a test running the new migration tool, migrating all 8-9TB and all apps and configuration from my own Synology 3617 Just wanted to try to see if I could create a full running backup on my Unraid server Sofar only thing that doesn't seem to work is my But again not sure I want to run virtual machines on a virtual NAS LOL! But anyway if someone knows how to fix this it could be fun to do a benchmark