benchee
Benchmarker
A tool for benchmarking Elixir code and comparing performance statistics
Easy and extensible benchmarking in Elixir providing you with lots of statistics!
1k stars
19 watching
66 forks
Language: Elixir
last commit: 15 days ago
Linked from 1 awesome list
benchmarkingelixirextensiblegraphsmicrobenchmarksstatistics
Related projects:
Repository | Description | Stars |
---|---|---|
alco/benchfella | Tools for comparing and benchmarking small code snippets | 516 |
joekain/bmark | A benchmarking tool for Elixir functions that uses statistical hypothesis testing to determine statistically meaningful changes in performance | 71 |
bencherdev/bencher | Tools and frameworks for continuous performance benchmarking of software systems | 554 |
bluss/bencher | A Rust benchmarking library that supports running and filtering benchmarks. | 85 |
python/pyperformance | An authoritative source of real-world benchmarks for Python implementations. | 869 |
davecheney/autobench | A framework to compare performance of Go versions | 99 |
evanphx/benchmark-ips | Provides an alternative to Benchmark's iteration per second benchmarking for Ruby code | 1,725 |
batate/shouldi | Provides Elixir testing libraries with nested contexts and improved test naming conventions | 135 |
krisselden/ember-macro-benchmark | An Ember application benchmarking tool to measure the effects of small changes on web applications. | 25 |
omerfarukz/webben | A cross-platform HTTP server benchmarking tool for performance testing and analysis. | 11 |
cloud-cv/evalai | A platform for comparing and evaluating AI and machine learning algorithms at scale | 1,771 |
shinmera/trivial-benchmark | A tool for quickly measuring performance of code snippets | 39 |
rebench/rebench.github.io | A platform providing reasonably accurate benchmarking results for JavaScript performance comparisons. | 44 |
healeycodes/websocket-benchmarker | Measures message throughput of WebSocket servers under load | 30 |
feyeleanor/gospeed | A library of micro-benchmarks for understanding and reasoning about the performance of Go programs. | 121 |