1. 02 Jul, 2014 3 commits
  2. 01 Jul, 2014 1 commit
  3. 30 Jun, 2014 3 commits
  4. 29 Jun, 2014 4 commits
  5. 28 Jun, 2014 7 commits
  6. 27 Jun, 2014 5 commits
  7. 26 Jun, 2014 6 commits
  8. 25 Jun, 2014 3 commits
  9. 23 Jun, 2014 1 commit
  10. 22 Jun, 2014 2 commits
    • Tatsuhiro Tsujikawa's avatar
      h2load: Set number of request per client explicitly · 5aba6e6d
      Tatsuhiro Tsujikawa authored
      Previously we do not specify the number of requests each client has to
      issue.  The each client corresponds to 1 TCP connection.  If
      connection was not accepted by server or not TLS handshake is not
      done, we effectively don't use that connection and the requests
      supposed to be issued for those connections are done via other
      established connections.  If this occurs, servers which do not accept
      all connections may gain good benchmark results since they don't have
      to pay extra cost to handle all connections (e.g., SSL/TLS handshake).
      This change explicitly set the number of requests each client has to
      issue so that servers cannot *cheat*.
      5aba6e6d
    • Tatsuhiro Tsujikawa's avatar
      Allocate header table ringbuffer lazily · 31de732e
      Tatsuhiro Tsujikawa authored
      Previously in inflater we reserve new ringbuffer when table size is
      changed.  This may be potentially a problem if new table size is very
      large number.  When inflater is not used directly by application, this
      is not a problem because application can choose the buffer size.  On
      the other hand, if application uses inflater directly and it does not
      have control of new buffer size (e.g., protocol dissector), then we
      just fail to allocate large buffer in
      nghttp2_hd_inflate_change_table_size() without actually use such huge
      buffer.  This change defers the actual allocation of buffer when it is
      actually needed so that we will fail when it is absolutely needed.
      31de732e
  11. 19 Jun, 2014 5 commits