Windows tuning, running the "server" Java VM (tuning)

[dcpotts]

Just like trini_tech, my default .conf file doesn't match the documentation above, and as a result, I'm not sure what to do.

Instead of copying and pasting from step 5 above, I uncommented the wrapper.java.additional etc... lines, so that I have:

# Java Additional Parameters
# Make sure the uncommented items are numbered sequentially
wrapper.java.additional.1=-Xmx768M
wrapper.java.additional.2=-Dcom.wowza.wms.AppHome="%WMSAPP_HOME%"
wrapper.java.additional.3=-Dcom.wowza.wms.ConfigHome="%WMSCONFIG_HOME%"
wrapper.java.additional.4=-Dcom.wowza.wms.ConfigURL=
wrapper.java.additional.5=-Dcom.sun.management.jmxremote=true
wrapper.java.additional.6=-Dorg.tanukisoftware.wrapper.WrapperManager.mbean=true
wrapper.java.additional.7=-Dorg.tanukisoftware.wrapper.WrapperManager.mbean.testing=false
# If running JDK, uncomment to run server environment (faster)
wrapper.java.additional.8=-server
# Better garbage collection setting to avoid long pauses
wrapper.java.additional.9=-XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:NewSize=1024m
wrapper.java.additional.10=-Djava.rmi.server.hostname=192.168.1.7
wrapper.java.additional.11=-Dcom.sun.management.jmxremote.port=1099
wrapper.java.additional.12=-Dcom.sun.management.jmxremote.authenticate=false
wrapper.java.additional.13=-Dcom.sun.management.jmxremote.ssl=false
wrapper.java.additional.14=-Dcom.sun.management.jmxremote.password.file="%WMSCONFIG_HOME%/conf/jmxremote.password"
wrapper.java.additional.15=-Dcom.sun.management.jmxremote.access.file="%WMSCONFIG_HOME%/conf/jmxremote.access"

...but now performance is slower than the default, especially for Cupertino streaming. I'm happy to run the default config, but the docs mention that this isn't recommended for production use.

[rrlanham]

Looks okay. Be careful with those GC options. The general tuning guide guide recommends not using special GC options unless you are having problems with memory.

Richard

[netbroadcasting]

How does the server version improve performance over the client version of the Java runtime. We have tested both and see little if any preformance differences.

Thanks

[charlie]

I believe it is just setting/config differences. The gc settings are better for shorter gc pauses but more frequent gc runs. The client is optimized for fast startup time.

Charlie

[multibc]

Hi,

is this necessary for WOWZA3 on WindowsServer2008R2?

I don't have the javacpl.cpl in system32
---------------------------------------------------------------------------------------------
3.Add the path to the Java Development Kit to your system PATH variable. You can do this by doing the following:a.Open the System Control Panel
b.Select the Advanced tab
c.Click the Environment Variables button
d.Double click the Path variable in the System variable section and add the full path the Java JDK bin folder inside the JDK folder surrounded by double quotes to the end of the list of path entries (path entries are separated by the ; character). For example, the string you add to the Path variable might look like this:
---------------------------------------------------------------------------
I cannot find b) and c) in W2008 so I cannot do d).

regards and thanks

-----------------------
I see there is no need to change anything. Actual JAVA is installed fine on W8R2 and no editing is necessar. Using cmdprompt tne java runtime could be called from everywhere in the system.
Is it necessary to remove the files anyway?
Do I have to write the rootpath? and where?
regars
----------------------------------

[randall]

Hi multibc,

The purpose of this thread is to ensure that you are running the "server VM" as opposed to the "client VM". In Windows this can be tricky because even though you install the JDK, some versions of Windows will still use the default "client VM" that comes with Windows.

You can run "java -server -version" in DOS (step 4) to see if your environment is set up to use the JDK or the JRE. You can only use the server flag when you are running the JDK.

If you do not see "Server VM" when you run that command, then you need to remove the JRE and install the JDK, and ensure that your PATH environment variable points to the JDK bin directory. You can search the net for how to set the path for your particular operating system. For example, you could search google for "How do I set the path in Windows 2008?"

[steveitl]

hello,
i have follow all points, so when start the server appear this question :
"Would you like the JAVA_HOME environment variable updated to point to this Java environment?"
this after modify point #3 in this guide. just press 'yes' and the server reset the variable path like :

C:\Program Files\Java\jdk1.7.0_01

is correct that the server resetting the value @ original condition ?

the path must be

C:\Program Files\Java\jdk1.7.0_01
to
C:\Program Files\Java\jdk1.7.0_01;"C:\Program Files\Java\jdk1.7.0_01\bin" ??

anyway, in the server logs appear :
CET comment server INFO 200 - Java Name: Java HotSpot(TM) 64-Bit Server VM

so, i'm sure that running server version ?

thanks
stefano

[randall]

"CET comment server INFO 200 - Java Name: Java HotSpot(TM) 64-Bit Server VM"

Ok, that looks good. You have it setup correctly.

JAVA_HOME = "C:\Program Files\Java\jdk1.7.0_01"

path = ";C:\Program Files\Java\jdk1.7.0_01\bin"

You'll want the path ENV var to point to the bin directory so you can run the java executable. This is different from the JAVA_HOME var which points to the directory containing bin.

[steveitl]

hello,
so, i need create a new entry : path = ";C:\Program Files\Java\jdk1.7.0_01\bin" in System Properties->Advanced->Environment Variables->Systems variables ??
i don't understand where i need put this path...

stefano

[randall]

You can search google for how to set the path for your OS.

You can see here for definition of path: http://en.wikipedia.org/wiki/Path_%28computing%29

You don't need to create a new one. There should be a "path" environment variable. You just need to append to it. Usually this is done when you install Java.