The httperf - HTTP load generator with post-quantum support from BoringSSL
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 

33 lines
1.6 KiB

  1. Some ideas (contributions/patches welcome):
  2. - port to libevent to improve scalability and deal with the file descriptor cap
  3. - Add option to output results as rdf (xml), cvs or default
  4. - Add ability to read entire POST and GET messages from logs and send them
  5. - wsesspage: don't fetch same object more than once (assume the existence
  6. of a cache)---this avoids trouble with recursive pages
  7. - make httperf easier to use; some ideas:
  8. o Make httperf into a network daemon that is controlled by
  9. an httperf frontend. This would allow running tests with
  10. a single command line even when multiple clients are involved.
  11. The performance results should be reported both on a
  12. per-client basis and in a summarized form reporting overall
  13. server behavior.
  14. o Provide (default) scripts to run certain benchmarks.
  15. o Provide (default) scripts to produce performance graphs.
  16. - use cycle registers to get time on CPUs that have such registers
  17. (IA-64, PA-RISC, x86, Alpha, at least)
  18. - randomize the uri's generated by --wset so we can defeat file prefetching
  19. that the server (or the server's OS) may attempt to do
  20. Done:
  21. + Specifying --session-cookie without specifying a session workload causes
  22. httperf to core-dump (reported by Dick Carter, 10/13/98)
  23. + elevate `Session' to same level as Call and Connection
  24. + sample session throughput when using sessions (not just rate throughput)
  25. + integrate Dick's wsesslog
  26. + write man-page
  27. + chunked replies fail after the first reply (at least on HP-UX)
  28. + core.c does not fully support pipelined requests yet; would require
  29. changes to the watchdog management