9 --> |
9 --> |
10 <!DOCTYPE concept |
10 <!DOCTYPE concept |
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
12 <concept id="GUID-D1B54263-1637-5D4E-8FE1-92612AB2851C" xml:lang="en"><title>What |
12 <concept id="GUID-D1B54263-1637-5D4E-8FE1-92612AB2851C" xml:lang="en"><title>What |
13 is Network Performance Testing? </title><shortdesc>The Network Performance Test suite (<i>NetPerf</i>) allows tests |
13 is Network Performance Testing? </title><shortdesc>The Network Performance Test suite (<i>NetPerf</i>) allows tests |
14 to be run that use the Symbian OS Communications Framework. The |
14 to be run that use the Symbian platform Communications Framework. |
15 purpose of the <i>NetPerf</i> is to measure and report the performance of |
15 The purpose of the <i>NetPerf</i> is to measure and report the performance |
16 the Symbian OS Communications Framework. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody> |
16 of the Symbian platform Communications Framework. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody> |
17 <p>The tests can be run on mobile devices or hardware reference boards. A |
17 <p>The tests can be run on mobile devices or hardware reference boards. A |
18 series of tests can be combined into a single script. The script is executed |
18 series of tests can be combined into a single script. The script is executed |
19 and the results analysed. Device creators and application developers use the |
19 and the results analysed. Device creators and application developers use the |
20 test results to analyse and optimise network performance on their hardware. |
20 test results to analyse and optimise network performance on their hardware. |
21 These tests are repeated on the same hardware to show the effects of optimisation |
21 These tests are repeated on the same hardware to show the effects of optimisation |
23 a benchmark. </p> |
23 a benchmark. </p> |
24 <p> <i>NetPerf</i> provides a common basis for collaborative work on network |
24 <p> <i>NetPerf</i> provides a common basis for collaborative work on network |
25 performance between Symbian and the device creators or application developers. <i>NetPerf</i> is |
25 performance between Symbian and the device creators or application developers. <i>NetPerf</i> is |
26 designed to run on <codeph>H2</codeph> and <codeph>H4</codeph> hardware reference |
26 designed to run on <codeph>H2</codeph> and <codeph>H4</codeph> hardware reference |
27 boards. <i>NetPerf</i> does not run on the emulator. The tests represent the |
27 boards. <i>NetPerf</i> does not run on the emulator. The tests represent the |
28 relative network performance that can be achieved by Symbian OS-based devices. |
28 relative network performance that can be achieved by Symbian platform-based |
29 This gives device creators a benchmark for their own hardware and adaptations. |
29 devices. This gives device creators a benchmark for their own hardware and |
30 Device creators can apply the same test program and scripts to different devices |
30 adaptations. Device creators can apply the same test program and scripts to |
31 to categorise them. </p> |
31 different devices to categorise them. </p> |
32 <p> <i>NetPerf</i> is driven by a <xref href="GUID-4D55E43C-B203-5145-9105-D75660D02E3B.dita">configuration |
32 <p> <i>NetPerf</i> is driven by a <xref href="GUID-4D55E43C-B203-5145-9105-D75660D02E3B.dita">configuration |
33 file</xref>. The configuration file specifies tests in terms of rate, direction |
33 file</xref>. The configuration file specifies tests in terms of rate, direction |
34 and packet size. This allows the test suite to emulate voice streams. This |
34 and packet size. This allows the test suite to emulate voice streams. This |
35 fulfils a common device creator request for information on the behaviour of |
35 fulfils a common device creator request for information on the behaviour of |
36 the network stack when streaming voice packets. It does not emulate the end-to-end |
36 the network stack when streaming voice packets. It does not emulate the end-to-end |
37 use case completely as there is no voice call control signalling. </p> |
37 use case completely as there is no voice call control signalling. </p> |
38 <section><title>NetPerf test suite components</title> <p>The following are |
38 <section id="GUID-21250CAF-01ED-483D-8D2E-F2AB3CCA6EE6"><title>NetPerf test suite components</title> <p>The following are |
39 the <i>NetPerf</i> test suite components: </p> <ul> |
39 the <i>NetPerf</i> test suite components: </p> <ul> |
40 <li id="GUID-F3837338-DCC6-5AC8-AA92-2C978A6AA062"><p> <xref href="GUID-D1B54263-1637-5D4E-8FE1-92612AB2851C.dita#GUID-D1B54263-1637-5D4E-8FE1-92612AB2851C/GUID-006E5816-65F0-50D4-80BD-CAA1D2408FF2"> UCC</xref> </p> </li> |
40 <li id="GUID-F3837338-DCC6-5AC8-AA92-2C978A6AA062"><p> <xref href="GUID-D1B54263-1637-5D4E-8FE1-92612AB2851C.dita#GUID-D1B54263-1637-5D4E-8FE1-92612AB2851C/GUID-006E5816-65F0-50D4-80BD-CAA1D2408FF2"> UCC</xref> </p> </li> |
41 <li id="GUID-A23AD4CE-8613-5009-8060-005121060BB6"><p> <xref href="GUID-D1B54263-1637-5D4E-8FE1-92612AB2851C.dita#GUID-D1B54263-1637-5D4E-8FE1-92612AB2851C/GUID-71E8B043-2917-5B77-B055-D0D366095905">TestExecute also known as TEF</xref> </p> </li> |
41 <li id="GUID-A23AD4CE-8613-5009-8060-005121060BB6"><p> <xref href="GUID-D1B54263-1637-5D4E-8FE1-92612AB2851C.dita#GUID-D1B54263-1637-5D4E-8FE1-92612AB2851C/GUID-71E8B043-2917-5B77-B055-D0D366095905">TestExecute also known as TEF</xref> </p> </li> |
42 <li id="GUID-79553BF1-7488-514D-8D63-11A1FF4E505E"><p> <xref href="GUID-D1B54263-1637-5D4E-8FE1-92612AB2851C.dita#GUID-D1B54263-1637-5D4E-8FE1-92612AB2851C/GUID-71B269BB-9A4A-57D4-A558-858A0492D416">TestExecute UCC plug-in</xref> </p> </li> |
42 <li id="GUID-79553BF1-7488-514D-8D63-11A1FF4E505E"><p> <xref href="GUID-D1B54263-1637-5D4E-8FE1-92612AB2851C.dita#GUID-D1B54263-1637-5D4E-8FE1-92612AB2851C/GUID-71B269BB-9A4A-57D4-A558-858A0492D416">TestExecute UCC plug-in</xref> </p> </li> |
43 <li id="GUID-DCBA552D-78EA-5EDC-9271-1D8D016DF447"><p> <xref href="GUID-D1B54263-1637-5D4E-8FE1-92612AB2851C.dita#GUID-D1B54263-1637-5D4E-8FE1-92612AB2851C/GUID-BDD35AF3-DDE6-5E23-9CD1-20C9EB96B0D1">TestDriver</xref> </p> </li> |
43 <li id="GUID-DCBA552D-78EA-5EDC-9271-1D8D016DF447"><p> <xref href="GUID-D1B54263-1637-5D4E-8FE1-92612AB2851C.dita#GUID-D1B54263-1637-5D4E-8FE1-92612AB2851C/GUID-BDD35AF3-DDE6-5E23-9CD1-20C9EB96B0D1">TestDriver</xref> </p> </li> |
59 from the supplied configuration file </p> </li> |
59 from the supplied configuration file </p> </li> |
60 <li id="GUID-E3EAA3C2-AD51-50E4-A745-64BF77161033"><p>invokes <i>TestDriver</i> </p> </li> |
60 <li id="GUID-E3EAA3C2-AD51-50E4-A745-64BF77161033"><p>invokes <i>TestDriver</i> </p> </li> |
61 <li id="GUID-548D295D-FD1D-5FCB-AC02-4E3783AFE5EF"><p>post-processes the <i>TEF</i> logs |
61 <li id="GUID-548D295D-FD1D-5FCB-AC02-4E3783AFE5EF"><p>post-processes the <i>TEF</i> logs |
62 to create a summary <i>CSV</i> file. </p> </li> |
62 to create a summary <i>CSV</i> file. </p> </li> |
63 </ul> <p><b>Delay Meter library </b> </p> <p>This is a plug-in layer for the communications |
63 </ul> <p><b>Delay Meter library </b> </p> <p>This is a plug-in layer for the communications |
64 framework that measures delays to the Bearer. It requires Symbian OS v9.5 |
64 framework that measures delays to the Bearer. </p> <p><b>TestExecute NetPerf plug-in </b> </p> <p>This plug-in performs the following: </p> <ul> |
65 or later with <i>Freeway</i> architecture. Delay measurements can be provided |
|
66 on earlier Symbian OS releases, if required, by using the <i>NetSTEB</i> tool. </p> <p><b>TestExecute NetPerf plug-in </b> </p> <p>This plug-in performs the following: </p> <ul> |
|
67 <li id="GUID-2AE9F834-9098-5258-86B8-F937DD59B94A"><p>Sends data packets </p> </li> |
65 <li id="GUID-2AE9F834-9098-5258-86B8-F937DD59B94A"><p>Sends data packets </p> </li> |
68 <li id="GUID-D9BC6822-08FA-59E1-A250-96BBE0EBFE3D"><p>receives data packets </p> </li> |
66 <li id="GUID-D9BC6822-08FA-59E1-A250-96BBE0EBFE3D"><p>receives data packets </p> </li> |
69 <li id="GUID-57C4B11F-F890-5E42-9DCE-01E9FFF284A9"><p>collects metrics, these |
67 <li id="GUID-57C4B11F-F890-5E42-9DCE-01E9FFF284A9"><p>collects metrics, these |
70 metrics are known as throughput or jitter </p> </li> |
68 metrics are known as throughput or jitter </p> </li> |
71 <li id="GUID-194CCCEA-AC69-553A-AA4F-F20665952471"><p>CPU usage meter </p> </li> |
69 <li id="GUID-194CCCEA-AC69-553A-AA4F-F20665952471"><p>CPU usage meter </p> </li> |
72 </ul> <p>If the <i>Delay Meter</i> library is configured, it collects and |
70 </ul> <p>If the <i>Delay Meter</i> library is configured, it collects and |
73 reports delay measurements. </p> <p><b>Sampling profiler </b> </p> <p>An optional component on the <i>DUT</i>, |
71 reports delay measurements. </p> <p><b>Sampling profiler </b> </p> <p>An optional component on the <i>DUT</i>, |
74 the <i>Sampling profiler</i> produces a log of the execution time spent in |
72 the <i>Sampling profiler</i> produces a log of the execution time spent in |
75 each function in the system. This allows the users to find any processing |
73 each function in the system. This allows the users to find any processing |
76 bottlenecks and identify possible optimisations. </p> </section> |
74 bottlenecks and identify possible optimisations. </p> </section> |
77 <section><title>NetPerf test mode</title> <p>The <i>NetPerf</i> tests can |
75 <section id="GUID-4E66FF6D-F3FC-4766-BA6F-FF196F715100"><title>NetPerf test mode</title> <p>The <i>NetPerf</i> tests can |
78 be run in two modes: </p> <ul> |
76 be run in two modes: </p> <ul> |
79 <li id="GUID-9229E4A5-3BB9-5508-A8F0-58E895FE0E1B"><p>Fully automatic - tests |
77 <li id="GUID-9229E4A5-3BB9-5508-A8F0-58E895FE0E1B"><p>Fully automatic - tests |
80 are started and controlled by the <i>Test Controller PC</i>. </p> </li> |
78 are started and controlled by the <i>Test Controller PC</i>. </p> </li> |
81 <li id="GUID-353B71C8-B5F2-54D1-89FB-E0A4CA69BD2C"><p>Semi-automatic - tests |
79 <li id="GUID-353B71C8-B5F2-54D1-89FB-E0A4CA69BD2C"><p>Semi-automatic - tests |
82 are built on the <i>Test Controller PC</i> and transferred to the <i>DUT</i>. |
80 are built on the <i>Test Controller PC</i> and transferred to the <i>DUT</i>. |
83 The <i>DUT</i> runs the tests. Results are copied back to the <i>Test Controller |
81 The <i>DUT</i> runs the tests. Results are copied back to the <i>Test Controller |
84 PC</i> for analysis. </p> </li> |
82 PC</i> for analysis. </p> </li> |
85 </ul> </section> |
83 </ul> </section> |
86 <section><title>Bearer Configuration</title> <p>Bearer configuration is to |
84 <section id="GUID-CD3B9054-17C4-4519-A242-7959D2C2B8E2"><title>Bearer Configuration</title> <p>Bearer configuration is to |
87 set up the communication bearers between the <i>DUT</i>, <i>Test Controller |
85 set up the communication bearers between the <i>DUT</i>, <i>Test Controller |
88 PC</i> and <i>Network Monitor PC</i>. The <i>NetPerf</i> test suite uses two |
86 PC</i> and <i>Network Monitor PC</i>. The <i>NetPerf</i> test suite uses two |
89 separate communication channels: control channel and bearer channel. These |
87 separate communication channels: control channel and bearer channel. These |
90 two channels can be merged into one bearer. </p> </section> |
88 two channels can be merged into one bearer. </p> </section> |
91 </conbody><related-links> |
89 </conbody><related-links> |