Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: Any updated version of JAVA VM Tuning? Last one was 2008

  1. #1

    Default Any updated version of JAVA VM Tuning? Last one was 2008

    Any updated version of JAVA VM Tuning document? Last one was created 2008 and it seems that a lot of the items on the [install-dir]/bin/WowzaMediaServerPro-Service.conf has changed and gets confusing matching what needs to be changed. This would make it easier for anybody to properly tune their JAVA VM configuration.


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

  2. #2
    Join Date
    Dec 2007
    Posts
    22,013

    Default

    Are you using Wowza 1.7x? That is the most recent guide for that version of Wowza, but some of the updates in thecurrent version, like GC options, are probably relevant. This is the current tuning guide for Wowza 3:

    http://www.wowza.com/forums/content....ormance-tuning

    Richard

  3. #3

    Default

    Richard,
    I am using 3.1.2.

    On point no. 4 of the link you sent, no. 4 (Windows tuning, running the "Server" JAVA VM) still does point to the link I posted which was done in 2008. Again, if you look at the code it is referring to, it might be refering to a 1.X.X version of WMS. A lot of the code it contains is obsolete. Can you provide a similar document which holds the latest version? Either for version 3.1.2 and/or 3.5. This just makes it easier for full paying customers like me to copy and paste the code instead of looking at every line and making guesses of what to change.

    4.It is best to run the -server version of the Java VM. The instructions for configuring the server version is described in these two forum threads:

    Linux and OSX tuning, running the "server" Java VM (tuning)
    Windows tuning, running the "server" Java VM (tuning)

  4. #4
    Join Date
    Dec 2007
    Posts
    22,013

    Default

    That is the current guide. It has been updated recently and many times since 2008. I'm not sure why it is showing that date

    Richard

  5. #5

    Default

    Richard,
    I still don't know if we're looking at the same file /code from WOWZA Media Server 3.1.2 but as far as my installation is concerned,whatever is written on the "updated" Windows tuning, running the "server" Java VM (tuning) is not the same as the current default configuration. When was this last updated to reflect the default configuration of the WowzaMediaServerPro-Service.conf?


    See below:
    WowzaMediaServerPro-Service.conf

    Windows tuning, running the "server" Java VM (tuning)
    # Java Additional Parameters
    # Java Additional Parameters
    wrapper.java.additional.1=-Dcom.wowza.wms.AppHome="%WMSAPP_HOME%"
    wrapper.java.additional.2=-Dcom.wowza.wms.ConfigHome="%WMSCONFIG_HOME%"
    wrapper.java.additional.3=-Dcom.wowza.wms.ConfigURL=
    wrapper.java.additional.4=-Dcom.sun.management.jmxremote=true
    wrapper.java.additional.5=-Dorg.tanukisoftware.wrapper.WrapperManager.mbean=true
    wrapper.java.additional.6=-Dorg.tanukisoftware.wrapper.WrapperManager.mbean.testing=false
    #wrapper.java.additional.7=-Dcom.sun.management.jmxremote.port=1099
    #wrapper.java.additional.8=-Dcom.sun.management.jmxremote.authenticate=false
    #wrapper.java.additional.9=-Dcom.sun.management.jmxremote.ssl=false
    #wrapper.java.additional.10=-Dcom.sun.management.jmxremote.password.file="%WMSCONFIG_HOME%/conf/jmxremote.password"
    #wrapper.java.additional.11=-Dcom.sun.management.jmxremote.access.file="%WMSCONFIG_HOME%/conf/jmxremote.access"
    #wrapper.java.additional.12=-Djava.rmi.server.hostname=192.168.1.7



    WOWZA 3.1.2
    # Java Additional Parameters
    # Make sure the uncommented items are numbered sequentially
    wrapper.java.additional.1=-Xmx768M
    wrapper.java.additional.2=-Dcom.wowza.wms.native.base="win"
    wrapper.java.additional.3=-Dcom.wowza.wms.runmode="service"
    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
    wrapper.java.additional.8=-Djava.net.preferIPv4Stack=true
    # If running JDK, uncomment to run server environment (faster)
    #wrapper.java.additional.9=-server
    # Uncomment to force Java to use specific language settings
    #wrapper.java.additional.10=-Duser.language=en
    #wrapper.java.additional.11=-Duser.country=US

  6. #6
    Join Date
    Dec 2007
    Posts
    22,013

    Default

    Okay, I will forward.

    Thanks for the report,
    Richard

  7. #7

    Default

    The article you are pointing to is very old. The updated tuning article is here:

    http://www.wowza.com/forums/content....general-tuning

    Charlie

  8. #8

    Default

    Charlie,
    Please look at the whole thread and the link that you gave again.


    Your link points to an "updated" tuning article. However, if you see the link Windows tuning, running the "server" Java VM (tuning) within that page, it points to an old version of JAVA TUNING.

    Can you point me directly to a link that has the following for tuning:



    WOWZA 3.1.2
    # Java Additional Parameters
    # Make sure the uncommented items are numbered sequentially
    wrapper.java.additional.1=-Xmx768M
    wrapper.java.additional.2=-Dcom.wowza.wms.native.base="win"
    wrapper.java.additional.3=-Dcom.wowza.wms.runmode="service"
    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=t rue
    wrapper.java.additional.7=-Dorg.tanukisoftware.wrapper.WrapperManager.mbean.t esting=false
    wrapper.java.additional.8=-Djava.net.preferIPv4Stack=true
    # If running JDK, uncomment to run server environment (faster)
    #wrapper.java.additional.9=-server
    # Uncomment to force Java to use specific language settings
    #wrapper.java.additional.10=-Duser.language=en
    #wrapper.java.additional.11=-Duser.country=US

  9. #9

    Default

    Hello,

    Is there any aricle with answer to xtian001's question? I am also trying to find same thing.

    Best regards

  10. #10

    Default

    It is referenced in the new tuning guide:

    Heap size:
    [install-dir]/bin/WowzaMediaServer-Service.conf (Windows Service)

    Code:
    wrapper.java.additional.1=-Xmx3000M
    and

    GC:

    [install-dir]/bin/WowzaMediaServer-Service.conf (Windows Service, add around line 36). For example:

    Code:
    wrapper.java.additional.[n]=-XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:NewSize=512m


    Note: Set [n] to the next available number in the list of wrapper.java.additional items. So if the last uncommented-out wrapper.java.additional item is 8 then this item needs to be one item below it with an index of 9.
    Charlie

Page 1 of 2 12 LastLast

Similar Threads

  1. updated server and installed java update - lost stream
    By JohnSmith in forum Live Streaming and Encoder Discussion
    Replies: 1
    Last Post: 03-28-2013, 03:50 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •