Changes between Version 8 and Version 9 of Testing

Timestamp:

03/15/13 06:42:13 (9 years ago)

Author:

Antoine Martin

Comment:

--

Testing

@@ -28 +28 @@
 It can also be useful to redirect the test's output to a log file to verify that none of the tests failed with any exceptions/errors (looking for exception messages in the log afterwards).
 At the moment it does not have a command line interface, and all the options have to be edited directly in the source file.
-One has to be very careful when interpreting the results, here are some examples of misleading statistics:
+[[BR]]
+Note: to take advantage of iptables packet accounting (mostly for comparing with VNC which does not provide this metric), follow the error message and setup iptables rules to match the port being used in the tests, ie: by default:
+{{{
+iptables -I INPUT -p tcp --dport 10000 -j ACCEPT
+iptables -I OUTPUT -p tcp --sport 10000 -j ACCEPT
+}}}
+Please also see:
+
+== Misleading Statistics ==
+One has to be very careful when interpreting performance results, here are some examples of misleading statistics:
 * higher CPU usage is not necessarily a bad thing if the framerate has increased
 * lower latency is good, but not if the highest latency is up
@@ -36 +45 @@
 * gtkperf tests really skew the results and should generally be excluded from sample data (or not run at all)
 * etc..
-
-[[BR]]
-Note: to take advantage of iptables packet accounting (mostly for comparing with VNC which does not provide this metric), follow the error message and setup iptables rules to match the port being used in the tests, ie: by default:
-{{{
-iptables -I INPUT -p tcp --dport 10000 -j ACCEPT
-iptables -I OUTPUT -p tcp --sport 10000 -j ACCEPT
-}}}