We are in the process of upgrading to Wowza Streaming Engine, but while we are still on 3.6.4, we are having memory retention issues consuming 88% memory and I thought I haven’t tested this in 4.2, I am concerned that the same thing will happen there.
I took a heapdump of the java process and surprisingly saw that the top consumers and heap retention are:
Class Name Shallow Heap Retained Heap Percentage Retained Heap
com.wowza.wms.httpstreamer.cupertinostreaming.livestreampacketizer.LiveStreamPacketizerCupertino @ 0x6a7b309f8 432 179717328 0.21372 179717328
com.wowza.wms.httpstreamer.sanjosestreaming.livestreampacketizer.LiveStreamPacketizerSanJose @ 0x67bc6fcb0 304 175720952 0.20897 175720952
com.wowza.wms.httpstreamer.cupertinostreaming.livestreampacketizer.LiveStreamPacketizerCupertino @ 0x6a7b2fac8 432 41947360 0.04988 41947360
com.wowza.wms.httpstreamer.sanjosestreaming.livestreampacketizer.LiveStreamPacketizerSanJose @ 0x67c580798 304 40966480 0.04872 40966480
com.wowza.wms.httpstreamer.smoothstreaming.livestreampacketizer.LiveStreamPacketizerSmoothStreaming @ 0x60cc2e4d8 352 40408176 0.04805 40408176
com.wowza.wms.httpstreamer.cupertinostreaming.livestreampacketizer.LiveStreamPacketizerCupertino @ 0x6aa83f720 432 22831336 0.02715 22831336
In summary, LiveStreamPacketizerCupertino and LiveStreamPacketizerSanJose are consuming 21% and 20% of the heap respectively and retaining. What could be causing this?
I have httpOriginMode enabled being pulled by EdgeCast for viewership consumption.