Improve Package installation time

Plex Media Server NAS & Devices
1

Hi Chuck, I have not tested any of these new packages, but I have a question/request or 2;

in the current/existing readynas x86 builds, there are 2 commands which run which take an increasing amount of time to complete as library size continues to grow;

(approximated from memory)

  • find (/pmspath)*.pyc -delete
  • chmod -r admin:admin (/pmspath)

is there any way that the find/delete can target the specific folder(s) that have *.pyc files in them instead of processing the entire pms path including metadata etc?

similarly chmod can also take a long time to progress through the directory tree with large libraries, is this necessary after every upgrade? wouldn’t the permissions stay the same once installed?

and lastly, would it be possible to restart the plex service after the package installer completes?

currently the after install completes, plex does not get restarted… so admin must install update, wait for all the file system activities to be processed above, then when the package install finally completes, restart plex manually.

plex upgrade can take 30-60+ minutes depending on nas load.

thanks for reading

Much faster (hopefully), smaller (mostly) and better PMS builds preview (1.15.0.573-123756e9a)
2

When I do a find-delete operation, I do it a bit differently.

find /path1 /path2 /path3  -name \*.xxx   -exec   action-to-do-here \;

If you want to use the -delete that’s fine.
Going through the directories themselves just takes a long time if you have a big library

I just reset my library (i’m always testing something) so let me do a full build up of my default and report back in a bit. Once done, we can quasi-benchmark it.

3

that looks similar, but it is the DEB installer that is performing these commands as part of some script (I assume) for the readynas package.

I am not doing anything other installing the .deb file via the readynas app installer/uploader

It is something that plex installer is doing, not me.

I see the commands happening via HTOP

4

This is the Seagate ReadyNas ?

I’m looking right now and not finding any of the actions you’re describing.

The PMS installer files are themselves empty except for

#!/bin/sh

exit 0
5

Maybe we should break this out into a separate discussion?

6

OK, but to clarify, netgear - readynas

plexmediaserver-ros6-binaries_1.14.0.5465-425e4ac90_amd64

7

Got it… yes… Looked at one thing, wrote the other. my mistake.

Yes, it’s there.
I didn’t write this installer so will need ask why it was done this way.
If the netgear behaves as the Synology does, I can update this to be selective about forcing a "set ownership’ like I do on Synology. It’s an easy fix…

Worst case, I do what is done on Synology, Push it to the background so the installation can proceed normally.

1 Like
8

@TeknoJunky

I’ve move us out here to a new thread.

This is a good improvement which can be had for the NAS.
It deserves to be a free-standing thread.

9

thanks for your help!

10

Feedback:

The “chown” you see currently has been removed because it’s entirely unnecessary.
The change is visible now in the beta thread (which you haven’t tried)

The PYC cleanup is being worked and will be done before we release.

1 Like
11

Thank you sir!

Any word about restarting the pms service upon successful update? :grinning:

12

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.