We have tested all versions of 4.0-4.0.6. Each time, had to revert back to version 3.6.4.
We have notice memory usage is much higher on Wowza 4.0.6 compared to 3.6.4. Can this be true? The issues we are having is our Roku platform is encountering “Loading, please wait” issues or Roku would simply disconnect from edge servers. Is it possible the memory is maxing on our origin and disconnects all the streams to Edge? Wowza support is telling us it is a network issue. We disagree because 3.6.4 worked perfectly.
Link to screenshot: https://www.dropbox.com/s/t8bowluo5dshwgm/max_memory.png?dl=0 Wowza uptime around 1 day and less than 300 connections, how can our memory max out at this load?
We are setup using liverepeater-origin/liverepeater-edge on Windows 2012 R2 servers. Each server consist of 16GB or ram, quad core.
Hi there,
The Wowza Heap bar indicates that it may be a memory leak and a heap dump of the running server may show where it is occurring.
Can you please open a support ticket with support@wowza.com and provide a description of the issue along with a link to this forum thread.
Please create a heap dump from the server using the process outlined here, How to take a Java heap dump. It will be a fairly large file so you will need to upload it to somewhere that we can download it from. Please include a download link in the support request.
Also, please zip up and include your conf, logs, transcoder/templates and manager/logs folders.
Note, if this is a linux server, the Total Memory bar in the graph also includes memory that is being used for OS level caching and network buffers. This memory is released automatically by the OS when required so can be considered as free memory however, Wowza has no way of separating the actual free memory from the cached memory so will always report higher than actual values for Total Memory.
You can use the linux free command to see actual memory usage. This page describes how to interpret the results.
If you have already opened a support ticket for this issue, then the Wowza support team will handle this through the ticket system.
Salvadore
Hi there,
The Wowza Heap bar indicates that it may be a memory leak and a heap dump of the running server may show where it is occurring.
Can you please open a support ticket with support@wowza.com and provide a description of the issue along with a link to this forum thread.
Please create a heap dump from the server using the process outlined here, How to take a Java heap dump. It will be a fairly large file so you will need to upload it to somewhere that we can download it from. Please include a download link in the support request.
Also, please zip up and include your conf, logs, transcoder/templates and manager/logs folders.
Note, if this is a linux server, the Total Memory bar in the graph also includes memory that is being used for OS level caching and network buffers. This memory is released automatically by the OS when required so can be considered as free memory however, Wowza has no way of separating the actual free memory from the cached memory so will always report higher than actual values for Total Memory.
You can use the linux free command to see actual memory usage. This page describes how to interpret the results.
If you have already opened a support ticket for this issue, then the Wowza support team will handle this through the ticket system.
Salvadore
We received response from support to change our liverepeater-origin to live. That resolve the memory issue. Is liverepeater-origin no longer supported in version 4?
Hi,
The difference between the live stream type and the liverepeater-origin stream type is that the live one will drop frames if it cannot deliver them quickly enough. The liverepeater-origin stream type won’t drop frames as it assumes that the origin & edges communicate on a good network that doesn’t have any latency or bandwidth issues. It also process the streams faster so will add more CPU load.
The increased memory usage with the liverepeater-origin could be due to the edge connections buffering too much and instead of dropping frames, it stores them in memory until they can be delivered. If the edges can’t receive the streams quickly enough, the memory usage will continue to increase.
Roger.
It is still supported,
This guide shows how to configure a live stream repeater:
How to configure a live stream repeater
The origin needs to be an application type of “live” and the edge needs to be “live-edge”
Salvadore
