How to get PS3MS to use Java 64 bit instead of 32 bit

[SuperDre]

How can you actually tell if PS3MS is using the 64bit version? and doesn't it also require 64bit versions of FFMpeg etc? or are they already part of the download?

[Simmo]

How can you actually tell if PS3MS is using the 64bit version? and doesn't it also require 64bit versions of FFMpeg etc? or are they already part of the download?

look in taskmgr (assuming youre using windows), if you're using the x86 version it'll list the loaded copy of java as "java.exe*32", if you're using the x64 version it wont have the *32 suffix; not sure on OSX or *nix

Cheers, Simmo

[sammysamsam]

Coltaine79,

Were you gonna post that file? i am curious to try it out.

[jazz]

Coltaine79,

Were you gonna post that file? i am curious to try it out.

I'd love to check that out too..

cheers

[Coltaine79]

I apologize profusely for not responding to this thread... I sorta left the world of PS3MS for about a month...

Currently, I'm not running PMS as a service (I didn't like the complete absence of a GUI) so I won't touch on that. However I will provide some pointers for those of you who want to run it on a 64-bit Java Virtual Machine.

Requirements:
64-bit Intel or AMD CPU (x86-64)
64-bit Windows (Win7 in my example)
at least 4GB of RAM
64-bit JVM installed
- look in the manual downloads section of java.sun.com
- the filename should be jre-6u21-windows-x64.exe
- it should install to C:\Program Files\Java
PS3 Media Server latest official beta installed (pms-setup-windows-1.20.409-BETA.exe)
- have not yet tried this with the Community Builds


Create a text file with the following contents and save it to your PS3 Media Server folder root as runme64.cmd:

Code: Select all

@echo off
"C:\Program Files\Java\jre6\bin\javaw.exe" -classpath update.jar;pms.jar;plugins/;plugins/* -Xmx2048M -Djava.net.preferIPv4Stack=true -Djava.encoding=UTF-8 net.pms.PMS


i.e. for me it is here: C:\Program Files (x86)\PS3 Media Server\runme64.cmd

Create a shortcut on your desktop (or whatever) pointing to the above CMD file. Make sure the shortcut will run from the same directory. Example, using my Windows 7 shortcut:

TARGET: "C:\Program Files (x86)\PS3 Media Server\runme64.cmd"

START IN: "C:\Program Files (x86)\PS3 Media Server"

Now, run the shortcut. PS3 Media Server will run in a 64-bit JVM with a 2GB heapsize! You should also be able to safely set the transcode buffer to 500 or 600. Personally, I didn't need anything that big, I just used 400. And with a 400MB transcode buffer, 2GB heapsize is probably overkill... you can change the 2048 in the batch file above to 1536 if you like.

Here's a screenshot of Process Explorer on my system with the whole setup going, while I watch a subtitled xvid movie through the [Avisynth/MEncoder] option.
Unfortunately we're still using 32-bit versions of all the other EXEs (like MEncoder) but due to the 64-bit JVM at least we can benefit from the larger heapsize.



Enjoy!

[gatsby]

Fantastic post Coltaine79! Thanks

[radamo]

Is there an advantage to using the 64 bit java client? Can't find any info on this.
Thanks,
RA

[meskibob]

In the case of PMS not really (heap isn't that large)...
http://www.oracle.com/technetwork/java/ ... erformance

[radamo]

First off, thanks to Coltaine79 for a great post.

meskibob,
Informative link. I don't understand why but, using 64bit java (set i up last night) my PS3MS seems smoother and I had NO glitches or DLNA errors in over 3 hours of straight usage. I am doing simple stuff streaming music and slide shows. My issue seem to be related to the fact that my audio is all uncompressed m4a (Apple Lossless) files which tend to be fairly large and my pictures range from 500K jpg's up to 25 MB tiff's. Even though my throughput shows at 512MB to the PS3 I get many DLNA errors when working with these file sizes. Using 64bit java and 1536 for the heap size seemed to make it seamless.
RA

[mazey]

is anyone else having this problem when using 64 bit java to run ps3 media server,

http://code.google.com/p/ps3mediaserver ... ail?id=948

i noticed the 32 bit java doesnt have this problem, now im abit iffy about using 64 bit again.