We developed a small tool to calculate the goodput
of different basket2 padding methods. The goodput is calculated by parsing the
basket2proxy.log
and looking for the following line:
Please note that the format is modified from the original basket2 output by including the padding method. The goodput tool goes over the log and aggregates the data per padding method. From 1,000 connections per method, the output is:
The output format per method is mean±stddev median
and breaks it into
receive and transmit metrics from the perspective of the basket2 instance that
generated the log (client or server). For example, we see here that even for
Null padding receiving (for a server) has goodput 95% while transmit has 97%
goodput. Further, we see that all methods (that should be used) have significant
impact on goodput. The APE method is a new padding method and the subject of the
next update.