The Terramaster F4-210 NAS server offers many ways to interact with well known online services. In short you will find the following pre-compiled apps with the following categories:

Backup

• Alibaba Cloud OSS Sync
• Amazon S3 Sync
• AOMEI Backupper
• Box Sync
• Dropbox Synce
• Duple Backup Vault
• Duple Backup
• Google Drive Synce
• Koofr Synce
• Megadisk Synce
• OneDrive Synce
• OpenDrive Synce
• pCloud Synce
• USB copy
• Yandex Disk Synce

Business

• Docker
• Mail Server
• WordPress

Tools

• Apache Tomcat
• Git
• Java Virtual Machine
• MariaDB
• Node.js
• phpMyAdmin
• Python3
• SVN Server

Multimedia

• DLNA Media Server
• Emby Server
• Itunes Server
• Plex Media Server

Security

• Clam Antivirus
• Snapshot

Utilities

• Aria2
• BackBlaze B2 Sync
• chryrp
• coppermine
• e107_cms
• FreshRSS
• IceHrm
• iSCSI Target
• Joomla
• LimeSurvey
• MantisBT
• Matomo
• MyBB
• Net2FTP
• opencart
• OrangeHrm
• PDF Reader
• phpBB
• PodcastGenerator
• PrestaShop
• Transmission
• Text Editor
• Vtiger CRM
• Web Server

In our case we installed the Plex Media server app to test its performance.

As it seems the compatibility of the F4-210 NAS server with the Plex Media Server is limited to software transcoding SD/HD 720p and some HD 1080p files. 4K media serving is not supported due to harware limitations. Also hardware accelerated transcoding also isnt supported (only with Intel based systems) as the official Plex compatibility page shows.

Setup the Plex Media Server is rather easy after installing the plug-in you need to get into the desktop area of NAS and you will find an icon at the bottom left area. From there you can start the setup process. Via the local network we trasferred our data to the /public folder for the NAS server and into the Plex Media Server we added a libary with the following path (/mnt/md0/public/Media) to be possible to scan your media files.

When installing the Plex server we got around 36% cpu usage.

The performance when copying files was very good with almost full local 1Gbit network bandwitdh and around 45% cpu usage.

When playing an 1080p x265 source file over local ethernet network, the system cpu usage was around 100% and with frequent video drops (automatic), making it impossible to view. The system also alerted us with a notification about very high cpu usage:

Switching to 1080p x264 source files,things become much easier with around 3~10% cpu usage with original file quality. Copying and playback at the same time 1080p x264 file seems to produce around ~75% cpu usage which doesnt affect playback performance.

Passing to more advanced tests we can see that the 1080p x264 content is playable and even multi-channel audio files aren't an issue with the Plex media server. On the other hand x265 files aren't playable at all, even with low bitrate files.