Hi guys have my server set up using a Netcups RS1000 root server specs below:
Intel® Xeon® Gold 6140
Cores: 2 dedicated
Main memory DDR 4 ECC:8 GB
I have everything loading very quick and videos loading within 3-5 seconds, however I am having issues playing 4K films via direct play which are freezing every 15-20 seconds. Is it the fact that the server I have is not fast enough for 4k films streaming from G suite?? My home internet speed is 35-40Mb/s depending on time of day. I noticed if I leave TrueHD on the server will direct play the video and transcode the audio and the film will play perfectly fine. I assume because this is giving the server the chance to place the film into cache before.
My rclone config below: I have removed the client id,secret,google token and my plex server ip address and login for security purposes. What could the main issue be here cause It is racking my brains out! Thank you.
Sorry totally new to rclone i have edited rclone config and created gdrive and gcache has my first posta shows these credentials. What am I missing? I was under the assumption rclone would allready be mounted? thank you.
using this “ls /mnt/gdrive”
then it is showing me all directories on my gdrive where my content is. but if i run “sudo service rclone status” i get “Unit rclone.service could not be found.” if i run “sudo service unionfs status” i get the below:
Jan 24 19:57:30 v220181070318746-- systemd: Starting UnionFS Daemon…
Jan 24 19:57:40 v220181070318746-- systemd: unionfs.service: Found left-over process 1219 (unionfs) in control group while starting unit. Ignoring.
Jan 24 19:57:40 v220181070318746-- systemd: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jan 24 19:57:40 v220181070318746-- systemd: Started UnionFS Daemon.
I would set your Gdrive chunk size to be equal (or higher) than your cache chunk size.
Otherwise you are transferring each chunk to the cache in 2 parts but it won't be accessible until both are done. Inefficient...
upload_cutoff = 32MB
chunk_size = 32MB
EDIT: I'm sorry, these settings will ONLY affect uploads. I'm not sure what I was thinking when I first wrote this =P
For high bitrate 4K you may also want to experiment with setting cache chunks up a notch to 64MB. high bitrate 4K will eat through those chunks very quickly and there has to be enough buffer to request more before it runs out to prevent playback-buffering. This will increase the time it takes to open media however, so setting limits higher than you actually need for smooth playback is not ideal.
You can forget about google's bandwidth being the issue. It can saturate my 150Mbit connection easily and I imagine that is nowhere close to the actual limit. Wouldn't worry about it at all unless you get a gigabit connection or something.
One more thing that may help: Increasing your cache workers a little (8 or 10). From observing how cache works it seems that when files are requested it grabs the same amount of chunks to try to keep in cache as you have workers - so more workers will effectively try to keep a few more segments ready in the cache. This may slightly affect the speed of opening files too, but less than just increasing the chunk size I believe. Don't go too overboard on workers though. More is not automatically better.