I am running Plex Media Server on a Windows Server 2012 Essentials system and it shows up in Task Manager as a 32 bit process. Is there a 64 bit version of PMS? I cannot seem to find anything about this in the FAQs or forums.
1 Like
There is no 64bit version - PMS doesn't use that much memory so going 64bits wouldn't bring much benefit if any.
There is no 64bit version - PMS doesn't use that much memory so going 64bits wouldn't bring much benefit if any.
But 64bit is about more than just memory usage. No?
For real-time applications there are serious performance gains. Something like ProTools is doing real-time processing and transcoding. I've seen performance double when switching to 64bit mode.
2 Likes
But 64bit is about more than just memory usage. No?
For real-time applications there are serious performance gains. Something like ProTools is doing real-time processing and transcoding. I've seen performance double when switching to 64bit mode.
Pro Tools is in another dimension when it comes to processor and memory usage. Plex works fine under x86 so there's no need for x64.
so you mean because it run fine on x32 there is no need 2 improvement by developed x64 version?
Sent from my iPad
1 Like
The OSX version has gone 64 bit so I would imagine here is a need after all.
1 Like
I think the reason for OS X going that way is that Apple makes it a little more painful to run 32 bit apps. I'm not a Mac guy, but I believe that you have to take some special steps to run 32 bit apps. It might just be better practice to go 64 bit for Apple stuff. I believe since about 2011 that's been the standard.
1 Like
Mac, Crash Different... and that's all there is to say about that.
I see that most servers are now using 64 bit operating system. Why not release a 64-bit version, to speed up processing twice. When using 32 bit means we missed half the power of 64 bit.
Thank you!
Just going from 32-bit to 64-bit does not automatically double the speed. Most of what Plex does is just file handling, which will get very little boost in speed from 64-bit programming. The main grunt work is from the transcoder. The transcoder is based on FFMPEG. Here is a link to a site where a person compile FFMPEG into 64-bit from its native 32-bit. He only saw about a 10% improvement in speed. http://www.helyar.net/2014/compile-ffmpeg-64-bit-on-windows-with-msysmingw-w64/
1 Like
Just going from 32-bit to 64-bit does not automatically double the speed. Most of what Plex does is just file handling, which will get very little boost in speed from 64-bit programming. The main grunt work is from the transcoder. The transcoder is based on FFMPEG. Here is a link to a site where a person compile FFMPEG into 64-bit from its native 32-bit. He only saw about a 10% improvement in speed. http://www.helyar.net/2014/compile-ffmpeg-64-bit-on-windows-with-msysmingw-w64/
Thank you for giving me the useful information. But I'm still skeptical about it. So if a CPU supports 64 bit of technology. Then it will handle more packets than double the 32 bit. Maybe I have to do a test on my 64 bit Win 8.1 to see how.
Ah I have a small wonder is that. I found the software to convert them to handle apply of VGA technology to accelerate the process of it. So why do not we apply it to the Plex transcoding technology. If the Plex server using the VGA card will help it move faster code.
1 Like
Just going from 32-bit to 64-bit does not automatically double the speed. Most of what Plex does is just file handling, which will get very little boost in speed from 64-bit programming. The main grunt work is from the transcoder. The transcoder is based on FFMPEG. Here is a link to a site where a person compile FFMPEG into 64-bit from its native 32-bit. He only saw about a 10% improvement in speed. http://www.helyar.net/2014/compile-ffmpeg-64-bit-on-windows-with-msysmingw-w64/
Yes but we would remove the 2Gb Memory ceiling on PMS processes - which we are now easily reaching. We do need a 64-bit PMS app. But must first address any memory leak bugs as they would be harder to detect when the 2Gb limit is lifted
Thank you for giving me the useful information. But I'm still skeptical about it. So if a CPU supports 64 bit of technology. Then it will handle more packets than double the 32 bit. Maybe I have to do a test on my 64 bit Win 8.1 to see how.Ah I have a small wonder is that. I found the software to convert them to handle apply of VGA technology to accelerate the process of it. So why do not we apply it to the Plex transcoding technology. If the Plex server using the VGA card will help it move faster code.
Having a 64-bit system does not mean it can handle 2 32-bit packets simultaneously, it means it can handle packets up to 64-bit in size. A 64-bit program will provide some speed improvement in that it can read and write 64-bits of data at a time, but the work it does to that data still take the same amount of time. Here is a rough example.
32-bit system: Step 1, load 32-bit of data; Step 2 - process it; Step 3 - load next 32-bit of data; Step 4 - process it
64-bit system: Step 1, load 64-bit of data; Step 2 - process it (this takes the same amount of time as step 2 and 4 from above)
So you save the time from Step 3, but that step doesn't take up much CPU time, where as the processing part does, so overall you only get a slight bump in speed. There are some exceptions where the processing can be done faster with the 64-bit system, but these are limited to rare, complex computations.
Now for using the video card to process video, this has also been brought up and there are several posts about it. Basically ti comes down to the processor in the video cards are optimized to do certain types of math faster than a regular CPU. The math involved in transcoding audio and video does not take advantage of that so there would be little to no gains in speed having the video card do the work.
Yes but we would remove the 2Gb Memory ceiling on PMS processes - which we are now easily reaching. We do need a 64-bit PMS app. But must first address any memory leak bugs as they would be harder to detect when the 2Gb limit is lifted
I didn't know there was a limit for PMS. Considering it processing videos in small pieces, does it even use up that much memory to hit 2 GB? I've never noticed my memory usage going up very high.
I didn't know there was a limit for PMS. Considering it processing videos in small pieces, does it even use up that much memory to hit 2 GB? I've never noticed my memory usage going up very high.
Just get a client to do repeated requests for a library section with thousands of photos and soon there will be memory fragmentation and memory failures.
https://forums.plex.tv/topic/111771-please-help-plex-continues-to-crash-randomly/
https://forums.plex.tv/topic/85093-photos-not-shows-up/page-2#entry660844
A photo library of 80000 images with filter selection of say 25000 images running as slideshow would cause problems after a while - especially if abandoning the slideshow and re-starting or changing filters and doing a new request. The xml returned for the filtered objects is big.
Edit:
A lot of development effort went in by ljunkie into RARflix for the Roku to split the big filtered requests into smaller chunks of 3000 at a time and then re-build the master list for the slideshow but even with this, after a while the Plex Media Server ends up with memory fragmentation (on windows) and memory failures start. I hope that with 64-bit app and 8Gb/16Gb RAM for the Plex Media Server.exe process there would be less of an impact. Whilst I suspect memory leaks, the Plex Dev Team have not been able to prove that and think it is just fragmentation.
Accurate. If PMS login token configuration. Then when users watch video or image, it would require the server constantly. I get 26 to 37 from 1 IP connection while watching a video through Plex Web. So I think if people see more and constantly request, then Plex unresponsive sure that will happen.
Thank SA, but I'm not a PlexPass so I can't view that thread.
If there are memory leaks and fragmentation issues, going to 64-bit would just delay the inevitable.
25000 images for a slide show. At 1 sec each, that's almost 7 hours. That's 1 long slideshow.
Thank SA, but I'm not a PlexPass so I can't view that thread.
If there are memory leaks and fragmentation issues, going to 64-bit would just delay the inevitable.
25000 images for a slide show. At 1 sec each, that's almost 7 hours. That's 1 long slideshow.
This is an early non-PlexPASS forum post on the memory crashes with response;
I know memory leaks would just have their impact delayed with larger memory pool on 64-bit and so they ought to be eliminated first. Memory fragmentation - not sure what they can do about it
Yes would be a long slideshow but the beauty of RARflix and the Roku is that you can pause it independently of what you do on the TV and resume later. Also I found that RARflix and the Roku manage to cope with server outages and just resume later - it does not grumble - just stops and later carries on when the server is back.
I can have a slideshow for a filtered selection that would run over a number of days with my selected music tracks. I pause it when I want - switch to watching other TV sources and later resume. Don't have that luxury with the Samsung app
I have updated my earlier post to mention the changes Rob made to RARflix to cope with massive filtered requests
Thanks for the link. I wonder if a better implementation for a slideshow would be for Plex to convert it to a movie on the fly then just send over the movie. This would reduce the number of requests, which could potentially relieve this issue.
Thanks for the link. I wonder if a better implementation for a slideshow would be for Plex to convert it to a movie on the fly then just send over the movie. This would reduce the number of requests, which could potentially relieve this issue.
would make it very difficult to add music tracks on the fly to the slideshow - but an interesting thought !
Also needs then the shuffle option to be implemented at the PMS end which would be a good thing anyway
I read something about memory leaks in PMS in this post. I would like to report I've experiencing terrible memory leaks with PMS on Windows 7 64bit.
The issue verifies when I start Manual Refresh of one of my libraries. This library contains about 750 mkv files. Memory occupation goes from 2.2Gb to 7.2Gb then it stabilizes at 6.3Gb. The PC has AMD E350 Processor and 8Gb RAM Memory. Memory doesn't free up not even closing PMS. I need to restart the PC...
Is there any solution for this terrific problem?
Thank you...bye! :)
