1. 23 Feb, 2020 1 commit
  2. 21 Feb, 2020 1 commit
  3. 08 Aug, 2019 2 commits
  4. 03 Aug, 2019 1 commit
  5. 12 Jul, 2019 2 commits
  6. 28 Jun, 2019 1 commit
  7. 08 Mar, 2019 1 commit
    • Claudio Biagi's avatar
      Proxy performance fix, ticket #3439 · d41ed618
      Claudio Biagi authored
      Improve performance of the proxy forwarding batch of message.
      Add throughput benchmark for proxy.
      Fix valgrind error reported on unitialized vars
      RELICENSE: Add emtr grant
      d41ed618
  8. 13 Feb, 2019 1 commit
    • Shubham Lagwankar's avatar
      Problem: trie benchmarks count loop times instead of lookup calls (#3406) · 8ef72d48
      Shubham Lagwankar authored
      * Problem: trie benchmarks count loop times instead of lookup calls
      
      Solution: measure the time taken by each lookup call instead
      
      Other changes:
      - show average time taken and reduce other output
      - show number of keys, queries and key size before running the benchmark
      - use steady_clock as high_resolution_clock might not be steady
      - increase size of query set to 1M
      8ef72d48
  9. 09 Nov, 2018 1 commit
  10. 02 Feb, 2018 1 commit
  11. 11 Aug, 2017 2 commits
  12. 10 Aug, 2017 2 commits
  13. 03 Feb, 2016 1 commit
  14. 01 Feb, 2016 4 commits
  15. 28 Jan, 2016 1 commit
  16. 05 Jun, 2015 1 commit
  17. 02 Jun, 2015 1 commit
  18. 14 Oct, 2014 1 commit
  19. 31 Aug, 2014 1 commit
  20. 05 Jun, 2014 1 commit
  21. 04 Jun, 2014 1 commit
  22. 31 May, 2014 1 commit
  23. 02 Jan, 2014 1 commit
  24. 20 Sep, 2013 2 commits
  25. 15 Apr, 2013 2 commits
    • Pieter Hintjens's avatar
      9df7c70a
    • Pieter Hintjens's avatar
      I'm reverting the various changes to the throughput test programs since as far · c980820d
      Pieter Hintjens authored
      as I can see, these didn't work any more. At the very least, the command line
      API was broken and forced the user to enter new, exotic arguments. Patches
      should not break existing APIs. But also, the internals of these programs had
      become weird.
      
      If we want to build more complex performance tests, that's fine, but we should
      make new programs, not break the old ones. We need minimal, safe performance
      tests in 0MQ.
      
      Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
      please make the code neat, and build new APIs instead of breaking the old ones.
      
      Cheers
      Pieter
      c980820d
  26. 31 Mar, 2013 1 commit
  27. 05 Mar, 2013 1 commit
  28. 03 Mar, 2013 2 commits
  29. 26 Feb, 2013 1 commit
    • Attila Mark's avatar
      Improvements and fixes for performance of PUSH/PULL in local_thr and remote_thr. · a22714dd
      Attila Mark authored
      - option to set number of zmq threads on the command line for local_thr
      - option to set number of zmq_threads and workers in remote_thr
      - option to set SND/RCV buffer sizes on command line
      - option to set whether to PUSH/PULL on command line
      - option to set to use zmq_recv or zmq_msg for transfer on command line
      - better timing function
      - corrected and improved throughput reporting
      - HWM and DELAY socket options
      a22714dd
  30. 25 Feb, 2013 1 commit