We recently upgraded to 4.1 from 3.6.2 and added on Transcoder.
Our streams are running a lot worse than they were under the older version, with poor video quality and lots of viewers unable to connect or experiencing high rates of buffering.
Clients sending streams are getting disconnected multiple times as well. It has consistently happened since the day we rolled the upgraded version out live.
The Wowza recommended consultant we hired says nothing is wrong with the setup.
We contacted support who said it might be an issue with "garbage collection" and sent a few lines of code, but didn't explain where the code goes to try and fix the issue.
Here is what they sent:
If so, then the following commands could be added to implement ConcMarkSweep plus
This command pertains to tweaking your Java Virtual Machine. If you login to your Streaming Engine Manager, and go to Server > Performance Tuning > Java Settings, you would see the current mode set for your Garbage Collection (essentially how the memory used by Java is cleaned up). You can also view
an article that explains this more fully.
Another method you might want to try to resolve Transoder issues in version 4.1.1 is to upgrade to
version 4.1.2. There were some bug fixes that was specifically for some Transcoding issues. Here is a line on the
Release Notes for this version:
Fixed issue with parsing of H.264 and H.265 SEI packets when using Transcoder (didn't account for zero-length NAL units)