GitHub CodeQL vs Storage Benchmark Kit
GitHub CodeQL
codeql.github.comStorage Benchmark Kit
github.comSide by side
| Figure | GitHub CodeQL | Storage Benchmark Kit |
|---|---|---|
| Price from | $30/mo | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | — |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 5 | 1 |
| Spec score · Disk Benchmark Software | 8.3 (#4) | 7.5 (#19) |
| Purpose | CodeQL is a language and toolchain for code analysis that treats code as data. | SBK is a Java framework for measuring storage system throughput and latency with a common workload engine. |
Plans
GitHub CodeQL
- Free for research and open sourceFree
- GitHub Code Security$30 a month
- CodeQL for open source and researchFree
- GitHub Code Security$30 a month
- GitHub Free with CodeQL code scanningPrice not published
In their own words
GitHub CodeQL
GitHub CodeQL has no write-up on Specifiction yet; its figures are above.
Storage Benchmark Kit
Storage Benchmark Kit (SBK) is a Java framework for measuring storage-system throughput and latency with a shared workload engine. Its drivers cover object stores, message systems, databases, file systems, caches, and local queues. The harness controls concurrency, duration, rate, payloads, timestamps, and reporting. Results can be sent to the console, CSV, a local web console, Prometheus, or gRPC. PrometheusLogger exposes metrics, and SBK Dashboard supports Grafana dashboards and persistent time-series history. For distributed runs, SBK-GEM copies and launches SBK on remote hosts over SSH and aggregates measurements through an embedded SBM instance. YAML tools load arguments for single-node and distributed runs. SBK requires JDK 25; its wrapper can download a pinned OpenJDK 25 release and check its SHA-256 checksum. Automatic JDK installation supports Linux and macOS on x64 and AArch64, and Windows on x64. The Apache License 2.0 project is free. Its Local Web Console uses plain HTTP without authentication or TLS, so the project advises limiting exposure to a trusted benchmark network or SSH tunnel.