Results 1 to 6 of 6

Thread: Loadtool 4.0 - Live Stream fileCount Issue

  1. #1

    Default Loadtool 4.0 - Live Stream fileCount Issue

    According to the target server monitoring, I'm unable to produce playback streams no matter the value placed in the fileCount field. However, I am able to produce workerCount clients. Who has this working in 4 and what could possibly be the issue?

    I'm using Windows 7 (Wowza 4.0.4) as the client and the target is a RHEL6.5 with Wowza 4.0.3.
    I've followed the 4.0 guide to the letter. All machines have latest JDK's. All services and machines have been restarted and work with live-streaming accordingly.

    Tests.xml
    <Root>
    	<Tests>
    		<Test>
    			<Name>live</Name>
    			<ClassBase>com.wowza.wms.performance.remote.PerformanceRemoteClientTest</ClassBase>
    			<Properties>
    				<Property>
    					<Name>workerCount</Name>
    					<Value>2</Value>
    					<Type>Integer</Type>
    				</Property>
    				<Property>
    					<Name>fileCount</Name>
    					<Value>10</Value>
    					<Type>Integer</Type>
    				</Property>
    				<Property>
    					<Name>streamName</Name>
    					<Value>myStream</Value>
    				</Property>
    				<Property>
    					<Name>streamExt</Name>
    					<Value></Value>
    				</Property>
    				<Property>
    					<Name>vhostName</Name>
    					<Value>_defaultVHost_</Value>
    				</Property>
    				<Property>
    					<Name>connectionString</Name>
    					<Value>live/_definst_</Value>
    				</Property>
    				<Property>
    					<Name>bufferTime</Name>
    					<Value>3000</Value>
    					<Type>Integer</Type>
    				</Property>
    				<Property>
    					<Name>doRandom</Name>
    					<Value>false</Value>
    					<Type>Boolean</Type>
    				</Property>
    				<Property>
    					<Name>doRepeat</Name>
    					<Value>true</Value>
    					<Type>Boolean</Type>
    				</Property>
    				<Property>
    					<Name>ipAddress</Name>
    					<Value>172.18.224.16</Value>
    				</Property>
    				<Property>
    					<Name>ports</Name>
    					<Value>1935</Value>
    				</Property>
    			</Properties>
    		</Test>

  2. #2
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    To more easily debug, try running the client and target in stand-alone (/bin/startup.bat|sh) instead of the service so you can see log output in the consoles. You should see connections from the client in the target.

    Richard

  3. #3

    Default Loadtest: "Stream Create" null

    Quote Originally Posted by rrlanham View Post
    To more easily debug, try running the client and target in stand-alone (/bin/startup.bat|sh) instead of the service so you can see log output in the consoles. You should see connections from the client in the target.

    Richard
    Ok, I've set this up in standalone and captured the following logs (below). Am I supposed to send a live-stream to the client or target machines with an identical stream name (myStream) for the load simulation to work? If so, I've attempted this and get the same results on the target console: "INFO stream create - - " I've noticed the client machine log: "NetStream.Play.StreamNotFound". Again, please let me know if you see what the issue might possibly be.

    Client machine
    C:\Program Files (x86)\Wowza Media Systems\Wowza Streaming Engine 4.0.4\bin>perf
    ormance.bat live
    
    C:\Program Files (x86)\Wowza Media Systems\Wowza Streaming Engine 4.0.4\bin>perf
    ormance.bat live
    Tuning:  -Xmx4000M -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:NewSize=256m -se
    rver -Djava.net.preferIPv4Stack=true
    Configure logging: file:///C:/Program Files (x86)/Wowza Media Systems/Wowza Stre
    aming Engine 4.0.4/conf/log4j.properties
    INFO server comment - test: **** PerformanceRemoteClientTest *****
    INFO server comment - workerCount: 2
    INFO server comment - fileCount: 10
    INFO server comment - streamName: myStream
    INFO server comment - streamExt:
    INFO server comment - vhostName: _defaultVHost_
    INFO server comment - connectionStr: live/_definst_
    INFO server comment - doRandom: false
    INFO server comment - doRepeat: true
    INFO server comment - ipAddress: 172.18.224.16
    INFO server comment - ports: 1935
    INFO server comment - bufferTime: 3000
    INFO server comment - MediaCasterStreamValidator.init[live/_definst_]: Started
    INFO application app-start _definst_ live/_definst_
    INFO server comment - start [0]: 0
    INFO server comment - callConnect [0]: live/_definst_
    INFO server comment - connected [0]: 972442028
    INFO server comment - call play(first) [0]: myStream1
    INFO server comment - StreamOnStatus [0]: NetStream.Play.StreamNotFound
    INFO server comment - start [1]: 2
    INFO server comment - callConnect [1]: live/_definst_
    INFO server comment - connected [1]: 1802729315
    INFO server comment - call play(first) [1]: myStream2
    INFO server comment - StreamOnStatus [1]: NetStream.Play.StreamNotFound
    INFO server comment - totalBytes: 0
    INFO server comment - Status running:2 currBehind:0
    INFO server comment - Status running:2 currBehind:0
    INFO server comment - Status running:2 currBehind:0
    Terminate batch job (Y/N)? y
    
    C:\Program Files (x86)\Wowza Media Systems\Wowza Streaming Engine 4.0.4\bin>
    Target Machine
    [root@luwza01 bin]# 
    [root@luwza01 bin]# ./startup.sh
    Configure logging: file:///usr/local/WowzaStreamingEngine/conf/log4j.properties
    INFO server server-start Wowza Streaming Engine 4 Perpetual Edition 4.0.3 build10989 -
    INFO server comment - Server License Key: ENGP4-XXXXX-XXXXX-XXXXX-XXXXX-UKjQF
    INFO server comment - Maximum Connections: Unlimited
    INFO server comment - Maximum Incoming Streams: Unlimited
    INFO server comment - Transcoder Streams Available: 0
    INFO server comment - Transcoder Watermark: Yes
    INFO server comment - nDVR Available: No
    INFO server comment - DRM Available: No
    INFO server comment - HTTP Origin Available: Yes
    INFO server comment - Push Publish Available: Yes
    INFO server comment - REST API Available: No
    INFO server comment - Hardware Available Processors: 40
    INFO server comment - Hardware Physical Memory: 127237MB/129001MB
    INFO server comment - Hardware Swap Space: 2047MB/2047MB
    INFO server comment - Max File Descriptor Count: 20000
    INFO server comment - Open File Descriptor Count: 63
    INFO server comment - OS Name: Linux
    INFO server comment - OS Version: 2.6.32-431.11.2.el6.x86_64
    INFO server comment - OS Architecture: amd64
    INFO server comment - Java Name: OpenJDK 64-Bit Server VM
    INFO server comment - Java Vendor: Oracle Corporation
    INFO server comment - Java Version: 1.7.0_55
    INFO server comment - Java VM Version: 24.51-b03
    INFO server comment - Java Spec Version: 1.7
    INFO server comment - Java Home: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.55.x86_64/jre
    INFO server comment - Java Max Heap Size: 9767MB
    INFO server comment - Java Architecture: 64
    INFO server comment - Java Locale[user.language]: en
    INFO server comment - Java Locale[user.country]: US
    INFO server comment - Java Locale[file.encoding]: UTF-8
    INFO server comment - Java Timezone[user.timezone]: America/New_York
    INFO server comment - Java Args[0]: -Xmx10000M
    INFO server comment - Java Args[1]: -XX:+UseConcMarkSweepGC
    INFO server comment - Java Args[2]: -XX:+UseParNewGC
    INFO server comment - Java Args[3]: -XX:NewSize=512m
    INFO server comment - Java Args[4]: -Djava.net.preferIPv4Stack=true
    INFO server comment - Java Args[5]: -Dcom.sun.management.jmxremote=true
    INFO server comment - Java Args[6]: -Dcom.wowza.wms.runmode=standalone
    INFO server comment - Java Args[7]: -Dcom.wowza.wms.native.base=linux
    INFO server comment - Java Args[8]: -Dcom.wowza.wms.AppHome=/usr/local/WowzaStreamingEngine
    INFO server comment - Java Args[9]: -Dcom.wowza.wms.ConfigURL=
    INFO server comment - Java Args[10]: -Dcom.wowza.wms.ConfigHome=/usr/local/WowzaStreamingEngine
    INFO server comment - Server runmode: standalone
    INFO server comment - Server native.platform: linux
    INFO server comment - Server threads[h/t]: 600/400
    INFO server comment - RESTServer: Bind attempt ([any]:8087)
    INFO server comment - RESTServer: Bind successful ([any]:8087)
    INFO server comment - Wowza REST API started
    ERROR server comment - REST API: Server request (GET): IP WhiteList blocked (172.18.224.16)-403: http://172.18.224.16:8087/v1/server/server
    INFO server comment - RESTServer: Using configs from:/usr/local/WowzaStreamingEngine/
    INFO server comment - RESTServer: SSL:No
    INFO server comment - RESTServer: BasicAuth:No
    INFO server comment - RESTServer: Digest:Yes
    INFO server comment - RESTServer: XML Viewer:No
    INFO server comment - CMDInterface now listening: [any]:8083
    INFO server comment - MediaCache[MediaCache]: Thread pool size: [writer/readahead]:24/12
    INFO server comment - MediaCache[MediaCache]: MAX Pending size: [writer/readahead]:500M/25M
    INFO server comment - MediaCache[MediaCache]: Add store: path:/usr/local/WowzaStreamingEngine/mediacache maxSize:10737418240
    INFO server comment - MediaCache[MediaCache]: Add source[dvrorigin]: prefix:dvrorigin/ basePath:http://
    INFO server comment - MediaCache[MediaCache]: Flushing cache: start
    INFO server comment - MediaCache[MediaCache]: Flushing cache: done
    INFO server comment - MediaCache[MediaCache]: Start MediaCache GC
    INFO server comment - MediaCache[MediaCache]: Started
    INFO vhost vhost-start _defaultVHost_ -
    INFO server comment - _defaultVHost_ threads[h/t]:0/0 home:/usr/local/WowzaStreamingEngine
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:1935:24)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:1935)
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:8086:4)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:8086)
    INFO server comment - Server.startShutdownHook: Start server shutdown hook
    INFO server comment - StatsManager:startManager() Enabled=true
    INFO server comment - Wowza Streaming Engine is started!
    INFO server comment - MediaCasterStreamValidator.init[live/_definst_]: Started
    INFO application app-start _definst_ live/_definst_
    INFO session connect-pending 10.7.90.18 -
    INFO session connect 10.7.90.18 -
    INFO stream create - -
    INFO session connect-pending 10.7.90.18 -
    INFO session connect 10.7.90.18 -
    INFO stream create - -
    
    INFO application app-start _definst_ live/_definst_
    INFO session connect-pending 10.7.90.18 -
    INFO session connect 10.7.90.18 -
    INFO stream create - -
    INFO session connect-pending 10.7.90.18 -
    INFO session connect 10.7.90.18 -
    INFO stream create - -
    INFO stream destroy myStream1 -
    INFO stream destroy myStream2 -
    INFO session disconnect 173608077 -
    INFO session disconnect 262158409 -
    INFO session connect-pending 10.7.90.18 -
    INFO session connect 10.7.90.18 -
    INFO stream create - -
    INFO session connect-pending 10.7.90.18 -
    INFO session connect 10.7.90.18 -
    INFO stream create - -
    INFO stream destroy myStream1 -
    INFO stream destroy myStream2 -
    INFO session disconnect 2095516923 -
    INFO session disconnect 1749919413 -
    INFO application app-stop _definst_ live/_definst_
    INFO server comment - MediaCasterStreamValidator.init[live/_definst_]: Started
    INFO application app-start _definst_ live/_definst_
    INFO session connect-pending 10.7.90.18 -
    INFO session connect 10.7.90.18 -
    INFO stream create - -
    INFO session connect-pending 10.7.90.18 -
    INFO session connect 10.7.90.18 -
    INFO stream create - -
    INFO stream destroy myStream1 -
    INFO stream destroy myStream2 -
    INFO session disconnect 1334677404 -
    INFO session disconnect 628590387 -
    clear
    ^CINFO server comment - ServerShutdownHook.run[shutdown]
    INFO server comment - MediaCache[MediaCache]: Stop
    INFO server comment - Wowza REST API stopped
    INFO server comment - StatsManager:stopManager() stopped
    INFO vhost vhost-stop _defaultVHost_ -
    INFO application app-stop _definst_ live/_definst_
    INFO server server-stop - -
    [root@luwza01 bin]# clear
    [root@luwza01 bin]# ./startup.sh
    Configure logging: file:///usr/local/WowzaStreamingEngine/conf/log4j.properties
    INFO server server-start Wowza Streaming Engine 4 Perpetual Edition 4.0.3 build10989 -
    INFO server comment - Server License Key: ENGP4-XXXXX-XXXXX-XXXXX-XXXXX-UKjQF
    INFO server comment - Maximum Connections: Unlimited
    INFO server comment - Maximum Incoming Streams: Unlimited
    INFO server comment - Transcoder Streams Available: 0
    INFO server comment - Transcoder Watermark: Yes
    INFO server comment - nDVR Available: No
    INFO server comment - DRM Available: No
    INFO server comment - HTTP Origin Available: Yes
    INFO server comment - Push Publish Available: Yes
    INFO server comment - REST API Available: No
    INFO server comment - Hardware Available Processors: 40
    INFO server comment - Hardware Physical Memory: 127258MB/129001MB
    INFO server comment - Hardware Swap Space: 2047MB/2047MB
    INFO server comment - Max File Descriptor Count: 20000
    INFO server comment - Open File Descriptor Count: 63
    INFO server comment - OS Name: Linux
    INFO server comment - OS Version: 2.6.32-431.11.2.el6.x86_64
    INFO server comment - OS Architecture: amd64
    INFO server comment - Java Name: OpenJDK 64-Bit Server VM
    INFO server comment - Java Vendor: Oracle Corporation
    INFO server comment - Java Version: 1.7.0_55
    INFO server comment - Java VM Version: 24.51-b03
    INFO server comment - Java Spec Version: 1.7
    INFO server comment - Java Home: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.55.x86_64/jre
    INFO server comment - Java Max Heap Size: 9767MB
    INFO server comment - Java Architecture: 64
    INFO server comment - Java Locale[user.language]: en
    INFO server comment - Java Locale[user.country]: US
    INFO server comment - Java Locale[file.encoding]: UTF-8
    INFO server comment - Java Timezone[user.timezone]: America/New_York
    INFO server comment - Java Args[0]: -Xmx10000M
    INFO server comment - Java Args[1]: -XX:+UseConcMarkSweepGC
    INFO server comment - Java Args[2]: -XX:+UseParNewGC
    INFO server comment - Java Args[3]: -XX:NewSize=512m
    INFO server comment - Java Args[4]: -Djava.net.preferIPv4Stack=true
    INFO server comment - Java Args[5]: -Dcom.sun.management.jmxremote=true
    INFO server comment - Java Args[6]: -Dcom.wowza.wms.runmode=standalone
    INFO server comment - Java Args[7]: -Dcom.wowza.wms.native.base=linux
    INFO server comment - Java Args[8]: -Dcom.wowza.wms.AppHome=/usr/local/WowzaStreamingEngine
    INFO server comment - Java Args[9]: -Dcom.wowza.wms.ConfigURL=
    INFO server comment - Java Args[10]: -Dcom.wowza.wms.ConfigHome=/usr/local/WowzaStreamingEngine
    INFO server comment - Server runmode: standalone
    INFO server comment - Server native.platform: linux
    INFO server comment - Server threads[h/t]: 600/400
    INFO server comment - RESTServer: Bind attempt ([any]:8087)
    INFO server comment - RESTServer: Bind successful ([any]:8087)
    INFO server comment - Wowza REST API started
    ERROR server comment - REST API: Server request (GET): IP WhiteList blocked (172.18.224.16)-403: http://172.18.224.16:8087/v1/server/server
    INFO server comment - RESTServer: Using configs from:/usr/local/WowzaStreamingEngine/
    INFO server comment - RESTServer: SSL:No
    INFO server comment - RESTServer: BasicAuth:No
    INFO server comment - RESTServer: Digest:Yes
    INFO server comment - RESTServer: XML Viewer:No
    INFO server comment - CMDInterface now listening: [any]:8083
    INFO server comment - MediaCache[MediaCache]: Thread pool size: [writer/readahead]:24/12
    INFO server comment - MediaCache[MediaCache]: MAX Pending size: [writer/readahead]:500M/25M
    INFO server comment - MediaCache[MediaCache]: Add store: path:/usr/local/WowzaStreamingEngine/mediacache maxSize:10737418240
    INFO server comment - MediaCache[MediaCache]: Add source[dvrorigin]: prefix:dvrorigin/ basePath:http://
    INFO server comment - MediaCache[MediaCache]: Flushing cache: start
    INFO server comment - MediaCache[MediaCache]: Flushing cache: done
    INFO server comment - MediaCache[MediaCache]: Start MediaCache GC
    INFO server comment - MediaCache[MediaCache]: Started
    INFO vhost vhost-start _defaultVHost_ -
    INFO server comment - _defaultVHost_ threads[h/t]:0/0 home:/usr/local/WowzaStreamingEngine
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:1935:24)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:1935)
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:8086:4)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:8086)
    INFO server comment - Server.startShutdownHook: Start server shutdown hook
    INFO server comment - StatsManager:startManager() Enabled=true
    INFO server comment - Wowza Streaming Engine is started!
    INFO server comment - MediaCasterStreamValidator.init[live/_definst_]: Started
    INFO application app-start _definst_ live/_definst_
    INFO session connect-pending 10.7.90.18 -
    INFO session connect 10.7.90.18 -
    INFO stream create - -
    INFO session connect-pending 10.7.90.18 -
    INFO session connect 10.7.90.18 -
    INFO stream create - -
    INFO stream destroy myStream1 -
    INFO stream destroy myStream2 -
    INFO session disconnect 972442028 -
    INFO session disconnect 1802729315 -
    INFO application app-stop _definst_ live/_definst_

  4. #4
    Join Date
    Jun 2012
    Posts
    723

    Default

    Hi,

    I noticed that you have configured the Test.xml file to use a fileCount of 10.
    According to the Load Test Tool documentation here is what the fileCount parameter is used for:
    fileCount: Number of different stream names to play. If set to 0 (zero), then only a single stream is played by all client connections. The stream name is derived by concatenating [streamName] and [streamExt]. If greater than zero, then the stream name will include an index value ([index]) that is between 1 and [fileCount].
    According to your settings, you will have to publish 10 streams to your target server (myStream1, myStream2, .... myStream10) because the client machine will try to request those streams in order to generate load on the target machine.
    If you wish to publish only one stream (myStream) on the Target machine, and have all your clients connect to that one stream, then you will have to use a fileCount value of "0".

    In either case, you do need to publish one or more streams on the target machine, so that the clients will have a Wowza target output stream where to connect and generate streaming load.

    I hope this is helpful.

    Zoran

  5. #5

    Default Client loadtest??

    Quote Originally Posted by zoran_u View Post
    Hi,

    I noticed that you have configured the Test.xml file to use a fileCount of 10.
    According to the Load Test Tool documentation here is what the fileCount parameter is used for:


    According to your settings, you will have to publish 10 streams to your target server (myStream1, myStream2, .... myStream10) because the client machine will try to request those streams in order to generate load on the target machine.
    If you wish to publish only one stream (myStream) on the Target machine, and have all your clients connect to that one stream, then you will have to use a fileCount value of "0".

    In either case, you do need to publish one or more streams on the target machine, so that the clients will have a Wowza target output stream where to connect and generate streaming load.

    I hope this is helpful.

    Zoran
    Thanks Zoran. So I assumed the filecount was a simulated client (player) load count, which leads me to ask how this is produced for live-stream? My objective is to increase player load to test the limits (bottleneck discovery) of the server resources. As you recommended, I've sent a live stream to the target server (myStream) and reduced the filecount to zero since it's a single client machine. How do I actually create a player load? I'm a bit green, so please bare with the ignoramous here. Thanks in advance!

  6. #6
    Join Date
    Jun 2011
    Posts
    1,037

    Default

    Hi,
    workerCount is the value you need to increase in Tests.xml to simulate players. Currently it's set at two (2), which is a good value to test that everything is
    setup correctly. But beyond that you can then increase this number to simulate connected players. Keep an eye on resources on the client side though
    as one machine can only simulate so many clients.

    Daren

Similar Threads

  1. Live Stream Play Back Issue.
    By shankar.ram@selectv.co in forum Live Streaming and Encoder Discussion
    Replies: 2
    Last Post: 06-20-2013, 03:03 AM
  2. Live stream record issue
    By Lelik1985 in forum General Forum
    Replies: 17
    Last Post: 01-09-2012, 06:13 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •