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

Thread: CPU load increased significantly

  1. #1

    Default CPU load increased significantly

    Hi,

    CPU load on Wowza 3.1.2 was ~50% now it has increased to around 80-90%.

    I followed the guide for tuning a while ago but it just jumped this week suddenly. It could be because of the update but I am unsure as to how to analyze the problem exactly. I am not transcoding any feed nor do I have any plugins set up.

    We have eight streams coming in and a maximum of 100 streams playing out on HLS and RTMP mostly.

    Thanks

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

    Default

    Did you overwrite tuning changes? Is it a dedicated Wowza server, or other things going on, or is it a VM?

    Richard

  3. #3

    Default

    I checked the tuning changes, they are still active. The server also serves as a LAMP server for a few domains.

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

    Default

    To monitor Wowza specifically, use JConsole

    http://www.wowza.com/forums/content....tart-guide#jmx

    Richard

  5. #5

    Default

    CPU load has gone up to 104%

    Will JMX let me identify the problem? It just seems weird, I actually did some more tuning and the load went up. Find below a copy of my setenv.sh:

    #!/bin/sh

    _EXECJAVA=java
    JAVA_OPTS="-d64 -Xmx6000M"

    # Uncomment to run server environment (faster), Note: will only work if server VM install, comes with JDL
    JAVA_OPTS="$JAVA_OPTS -server"

    # Can be a better GC setting to avoid long pauses
    JAVA_OPTS="$JAVA_OPTS -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:+UseParNewGC"

    # Uncomment to fix multicast crosstalk problem when streams share multicast port
    JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true"

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

    Default

    If you changed any of the GC options and the load went up, then undo that change. The recommended option is to not use any of those and just use -server flag. Show the startup lines from your access log.

    Richard

  7. #7

    Default

    JMX shows a CPU usage between 15-20%. Is top really that inaccurate?

    I had only the -server flag without -d64 or the GC set up and it was around 80-90%. Shouldn't I at least enable d64 as the server is 64 bit?

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

    Default

    Do what works best. One reason it is different is the java heap size setting, what Java reserves but doesn't necessarily use but looks in use to the OS.

    Richard

  9. #9

    Default

    But none of this would explain the jump in reserved CPU usage then? On Wowza 3.1.2 it was 50% and but with 3.5 it's higher. I will fiddle around and see what is best for me, but I was just wondering if maybe I missed something and due to that the load went up. Below is a copy of Wowza startup:

    Configure logging: file:///usr/local/WowzaMediaServer/conf/log4j.properties
    INFO server server-start Wowza Media Server 3 Monthly Edition 3.5.0 build2989 -
    INFO server comment - Server License Key: SVRM3-XXXXX-XXXXX-XXXXX-XXXXX-huAnN
    INFO server comment - Maximum Connections: Unlimited
    INFO server comment - Transcoder Streams Available: Unlimited
    INFO server comment - Transcoder Watermark: No
    INFO server comment - nDVR Available: Yes
    INFO server comment - DRM Available: Yes
    INFO server comment - Hardware Available Processors: 6
    INFO server comment - Hardware Physical Memory: 10461MB/15697MB
    INFO server comment - Hardware Swap Space: 8191MB/8191MB
    INFO server comment - Max File Descriptor Count: 20000
    INFO server comment - Open File Descriptor Count: 50
    INFO server comment - OS Name: Linux
    INFO server comment - OS Version: 2.6.32-279.14.1.el6.x86_64
    INFO server comment - OS Architecture: amd64
    INFO server comment - Java Name: OpenJDK 64-Bit Server VM
    INFO server comment - Java Vendor: Oracle Corporation
    INFO server comment - Java Version: 1.7.0_09-icedtea
    INFO server comment - Java VM Version: 23.2-b09
    INFO server comment - Java Spec Version: 1.7
    INFO server comment - Java Home: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.9.x86_64/jre
    INFO server comment - Java Max Heap Size: 5333MB
    INFO server comment - Java Architecture: 64
    INFO server comment - Java Locale[user.language]: en
    INFO server comment - Java Locale[user.country]: US
    INFO server comment - Java Locale[file.encoding]: UTF-8
    INFO server comment - Java Timezone[user.timezone]: Europe/London
    INFO server comment - Java Args[0]: -Xmx6000M
    INFO server comment - Java Args[1]: -Djava.net.preferIPv4Stack=true
    INFO server comment - Java Args[2]: -Dcom.sun.management.jmxremote=true
    INFO server comment - Java Args[3]: -Dcom.wowza.wms.runmode=standalone
    INFO server comment - Java Args[4]: -Dcom.wowza.wms.native.base=linux
    INFO server comment - Java Args[5]: -Dcom.wowza.wms.AppHome=/usr/local/WowzaMediaServer
    INFO server comment - Java Args[6]: -Dcom.wowza.wms.ConfigURL=
    INFO server comment - Java Args[7]: -Dcom.wowza.wms.ConfigHome=/usr/local/WowzaMediaServer
    INFO server comment - Server runmode: standalone
    INFO server comment - Server native.platform: linux
    INFO server comment - Server threads[h/t]: 10/10
    INFO server comment - JMX java.rmi.server.hostname: 50.7.242.122
    INFO server comment - JMX bind attempt service:jmx:rmi://50.7.242.122:8084/jndi/rmi://50.7.242.122:8085/jmxrmi
    INFO server comment - JMX password file: /usr/local/WowzaMediaServer/conf/jmxremote.password
    INFO server comment - JMX access file: /usr/local/WowzaMediaServer/conf/jmxremote.access
    INFO server comment - JMX bind successful
    INFO server comment - CMDInterface now listening: [any]:8083
    INFO vhost vhost-start _defaultVHost_ -
    INFO server comment - _defaultVHost_ threads[h/t]:320/240 home:/usr/local/WowzaMediaServer
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:554:4)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:554)
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:1935:4)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:1935)
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:8086:1)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:8086)
    INFO server comment - Server.startShutdownHook: Start server shutdown hook
    INFO server comment - Wowza Media Server is started!
    INFO application app-start _definst_ live/_definst_
    INFO cupertino connect 75107352 -
    INFO stream create haditvone.smil -

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

    Default

    I'm not sure. One thing to try, even though there is plenty of available memory, is reduce Java heap size a bit: try -Xmx5000M

    Richard

Page 1 of 2 12 LastLast

Similar Threads

  1. Many published streams, cpu load
    By qstream in forum General Forum
    Replies: 3
    Last Post: 04-13-2014, 08:02 PM
  2. CPU load increase in 3.6.2-p12 vs p10?
    By christr in forum General Forum
    Replies: 7
    Last Post: 09-27-2013, 12:17 PM
  3. cpu load problem-Is it normal?
    By jiwan2004 in forum Server Administration Discussion
    Replies: 2
    Last Post: 09-01-2012, 10:53 AM
  4. Redirect new connections based on current CPU load
    By daveuofu in forum General Forum
    Replies: 1
    Last Post: 03-07-2012, 10:45 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
  •