CupertinoMediaCasterConnection

Hello

We print the main source broadcasts to the wowza stream file with the wowza api service we have written, we print instant 1 to 20 source live broadcasts and get hls output, the duration of our source live broadcasts takes a maximum of 2 hours, the broadcasts we print from wowza constantly freeze, while the main source broadcast does not freeze at all,

I tried all the transcode options one by one, Transcode Transrate H265
There is no setting option left that I did not change in the performance tuning values
There is no value that I have not tried in the live application features, but the broadcasts are constantly cut off or freeze at 1-2 second intervals,

No matter what I did, I could not fix these errors in the logs,
I have a license, I am writing to support. Even though I send all the logs to whatever is requested, they are answered within 48 hours, but they are given evasive answers.

Error logs:

server feature:
Intel Xeon Processor E5-2650 v3 10 Core 25MB Cache 2.30GHz
1TB SSD
64GB Ram
1gbps

About Wowza Streaming Engine
Wowza Streaming Engine Version
4.8.17+1 (build 20211216162410)
Wowza Streaming Engine Manager Version
4.8.17+1 (build 20211216162410)
License
Wowza Streaming Engine 4 Subscription Edition
OS Windows Server 2016 (amd64)
Java Information
Java Version
9.0.4
Java VM Version
9.0.4+11
Java Architecture
64
Java Name
OpenJDK 64-Bit Server VM
Java Vendor
Oracle Corporation
Java Home
C:\Program Files (x86)\Wowza Media Systems\Wowza Streaming Engine 4.8.17+1\jre
Java Max Heap Size
32768MB

Java Garbage Collection Settings,
default
G1 (Garbage First) collector (recommended)
-XX:+UseParallelGC -XX:+UseNUMA
-XX:+UseG1GC -XX:MaxGCPauseMillis=100

Java Garbage Collection Settings, I tried 3 options, unfortunately I keep getting the same errors, exactly what values ​​do I need to change in order to use full according to this server feature. I would appreciate if there is a friend who understands wowza configuration that can help.

Blockquote Single Live conf/applicaationlive Application.xml

live Live true

Transcoding is a resource-intensive process. With the server specs that you specified you can maybe transcoder 2-5 streams concurrently, depending on the transcoding profile. Have a look at the CPU usage when you start 20 streams; most likely the CPU will be close to, or at 100% pretty much all the time.

Transcoding is not an obligatory feature for streaming. If your incoming streams are good enough to be distributed then you can turn off transcoding and only use packaging to HLS. Packaging alone doesn’t need a lot of capacity, so you’ll easily do 20 streams on that server. But if you need transcoding, then:

  1. A single Wowza Streaming Engine license is valid for up to 10 concurrent transcoding sessions. Although the server does not stop you from transcoding more than 10, you will have to contact customerservice@wowza.com or sales@wowza.com to discuss your options.

  2. To transcode 20 streams on a single server you will need 1 or 2 GPUs (Graphics Processing Units, aka. Hardware Acceleration), e.g. an NVidia Tesla or similar. Again, this depends on your transcoding profile and settings. The GPUs that I’ve tested can handle 15-20 streams concurrently. I recommend to either use 2 x GPU in your server, or to get a 2nd server (which also is a good idea from a fail-over POV)