Hello
We've been testing concurrent streams on the media server to ensure it can handle enough, however when testing we've found that all of our streams didn't finish correctly.
We had 16 concurrent streams recording to the server, which is our benchmark, but once the streams were called to stop, there was no response from the media server for 60 seconds until later it did return the Stream Unpublished event but the
Last time we tested this was in response to a similar issue here where we tested WCS 5.2.673 using same instance type and JVM options. We managed to test 16 streams easily here which is why it's our benchmark.
We're suspecting this time it's to do with the Java Heap Memory as we're not sure if it's being correctly configured on the new Linux 2 AMI.
WCS Version: 5.2.780 (Amazon Linux 2 AMI)
WebSDK: 0.5.28.2753.154
Amazon Instance Type: t3a.medium
WCS-Core Properties:
I've been unable to confirm if the Java Heap Size is configuring to 2Gb. Can you please confirm if the settings are correct, including if we should still be setting the Garbage Collector?
Also can you recommend a way for us to confirm the heap size setting? I've tried using the command below which is why I got concerned about it not setting correctly.
Cheers.
Linux Printout:
We've been testing concurrent streams on the media server to ensure it can handle enough, however when testing we've found that all of our streams didn't finish correctly.
We had 16 concurrent streams recording to the server, which is our benchmark, but once the streams were called to stop, there was no response from the media server for 60 seconds until later it did return the Stream Unpublished event but the
stream.getRecordInfo() method gotten from it had a null value instead of the recorded stream name, which is what it would normally return.Last time we tested this was in response to a similar issue here where we tested WCS 5.2.673 using same instance type and JVM options. We managed to test 16 streams easily here which is why it's our benchmark.
We're suspecting this time it's to do with the Java Heap Memory as we're not sure if it's being correctly configured on the new Linux 2 AMI.
WCS Version: 5.2.780 (Amazon Linux 2 AMI)
WebSDK: 0.5.28.2753.154
Amazon Instance Type: t3a.medium
WCS-Core Properties:
Code:
### JVM OPTIONS ###
-Xms2g -Xmx2g
#-Xcheck:jni
# Can be a better GC setting to avoid long pauses
-XX:+UseConcMarkSweepGC
-XX:NewSize=256m
#-XX:+CMSIncrementalMode
#-XX:+UseParNewGC"Also can you recommend a way for us to confirm the heap size setting? I've tried using the command below which is why I got concerned about it not setting correctly.
Cheers.
Linux Printout:
Code:
java -XX:+PrintFlagsFinal -version | grep -iE 'HeapSize|PermSize|ThreadStackSize'
intx CompilerThreadStackSize = 1024 {pd product} {default}
size_t ErgoHeapSizeLimit = 0 {product} {default}
size_t HeapSizePerGCThread = 43620760 {product} {default}
size_t InitialHeapSize = 65011712 {product} {ergonomic}
size_t LargePageHeapSizeThreshold = 134217728 {product} {default}
size_t MaxHeapSize = 1023410176 {product} {ergonomic}
size_t MinHeapSize = 8388608 {product} {ergonomic}
uintx NonNMethodCodeHeapSize = 5826188 {pd product} {ergonomic}
uintx NonProfiledCodeHeapSize = 122916026 {pd product} {ergonomic}
uintx ProfiledCodeHeapSize = 122916026 {pd product} {ergonomic}
size_t SoftMaxHeapSize = 1023410176 {manageable} {ergonomic}
intx ThreadStackSize = 1024 {pd product} {default}
intx VMThreadStackSize = 1024 {pd product} {default}