Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

60GB Cached RAM

Featured Replies

I have an issue in my Plex DVR system. I have 80BB server memory and am transcoding 2-4 TV streams at times as recordings. I am getting notifications that there is "not enough disk space to start the recording".

 

When I check my "Stats" page, I see 64GB of cache memory and only 4GB free. What would cause so much cached RAM, and is that the issue I am facing?

bigrig-diagnostics-20190624-1421.zip

If you are transcoding to the RAM Disk (/tmp) that could explain your symptoms. Try setting the transcode location to be mapped to your cache drive instead.

  • Author

Should I create a new share for this /mnt/cache/transcode?

11 hours ago, mihcox said:

Should I create a new share for this /mnt/cache/transcode?

I would, yes.  Do your worst, abuse the system and see how big the transcode folder gets, then add 10-15% and go back to using a RAM drive that is at least that large :)  assuming you have enough RAM.

 

don't about the caching, its normal... unused memory is wasted memory.... it's a unix thing.  No worries, the system gives it up for other use.

Edited by Abzstrak

23 hours ago, mihcox said:

Should I create a new share for this /mnt/cache/transcode?

I would highly recommend transcoding to cache instead of RAM.

 

While it's true that unused RAM is wasted RAM, I disagree with the notion that using it for transcode tmp makes it any less wasted.

While Plex isn't system critical, it's what I call "happiness critical" e.g. I would imagine the overall happiness level of your household to drop significantly if Plex refuses to stream (due to insufficient memory for transcode tmp) so you have to go in and try to fix stuff. So even though theoretically yes the system will give it up for other uses, the RAM is almost exclusive reserved for Plex; therefore, unless you stream 24/7, such reserved RAM is actually even more wasted during down time.

 

The original justification for running transcode tmp in RAM was due to concerns over SSD wear. Personally, I have found that concern to be completely unfounded. SSDs wears out very gracefully and lasts beyond their rated lifespan (except for Intel SSD). SSDs don't usually just die once reaching its limit (except for Intel SSD) but will simply reallocates bad cells and continues to use what is left.

 

 

Make a share on the cache or set the Transcode share to use the Cache?

48 minutes ago, presence06 said:

Make a share on the cache or set the Transcode share to use the Cache?

No need that complicated. Just map a folder in appdata (which should be on cache) to Plex and use it for transcode temp.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.