https://github.com/SigNoz/logs-benchmark Skip to content Toggle navigation Sign up * Product + Actions Automate any workflow + Packages Host and manage packages + Security Find and fix vulnerabilities + Codespaces Instant dev environments + Copilot Write better code with AI + Code review Manage code changes + Issues Plan and track work + Discussions Collaborate outside of code + Explore + All features + Documentation + GitHub Skills + Blog * Solutions + For + Enterprise + Teams + Startups + Education + By Solution + CI/CD & Automation + DevOps + DevSecOps + Case Studies + Customer Stories + Resources * Open Source + GitHub Sponsors Fund open source developers + The ReadME Project GitHub community articles + Repositories + Topics + Trending + Collections * Pricing [ ] * # In this repository All GitHub | Jump to | * No suggested jump to results * # In this repository All GitHub | Jump to | * # In this organization All GitHub | Jump to | * # In this repository All GitHub | Jump to | Sign in Sign up {{ message }} SigNoz / logs-benchmark Public * Notifications * Fork 2 * Star 52 Logs performance benchmark repo: Comparing Elastic, Loki and SigNoz signoz.io/blog/logs-performance-benchmark/ 52 stars 2 forks Star Notifications * Code * Issues 1 * Pull requests 0 * Actions * Projects 0 * Security * Insights More * Code * Issues * Pull requests * Actions * Projects * Security * Insights SigNoz/logs-benchmark This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository. main Switch branches/tags [ ] Branches Tags Could not load branches Nothing to show {{ refName }} default View all branches Could not load tags Nothing to show {{ refName }} default View all tags Name already in use A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch? Cancel Create 1 branch 0 tags Code * Local * Codespaces * Clone HTTPS GitHub CLI [https://github.com/S] Use Git or checkout with SVN using the web URL. [gh repo clone SigNoz] Work fast with our official CLI. Learn more. * Open with GitHub Desktop * Download ZIP Sign In Required Please sign in to use Codespaces. Launching GitHub Desktop If nothing happens, download GitHub Desktop and try again. Launching GitHub Desktop If nothing happens, download GitHub Desktop and try again. Launching Xcode If nothing happens, download Xcode and try again. Launching Visual Studio Code Your codespace will open once ready. There was a problem preparing your codespace, please try again. Latest commit @pranay01 pranay01 Update README.md ... 0b2451e Jan 23, 2023 Update README.md 0b2451e Git stats * 25 commits Files Permalink Failed to load latest commit information. Type Name Latest commit message Commit time elk Readmes updated Jan 18, 2023 plg Readmes updated Jan 18, 2023 signoz Readmes updated Jan 18, 2023 .gitignore signoz added Nov 4, 2022 README.md Update README.md Jan 23, 2023 View code Logs Benchmark Benchmark Key Findings: A summary Ingestion Query Storage Findings Version Info : README.md Logs Benchmark This repo contains the setup for the all the three stacks i.e SigNoz, ELK and PLG used for benchmarking. Each of the folders contains it's own set of instructions on how to run them. The results of the benchmark are published here benchmark Benchmark Key Findings: A summary For any log management tool to be efficient, the following three factors are very important. Ingestion Distributed cloud-native applications can generate logs at a humungous scale. Log management tools should be efficient at ingesting log data at scale. Query Logs help in troubleshooting, and troubleshooting should be fast. The end-user experience depends on how fast a user can query relevant logs. Storage Storage is costly and logs data is often huge. Log management tools need to be efficient in storing logs. Findings * For ingestion, we found SigNoz to be 2.5x faster than ELK and consumed 50% less resources. * For querying benchmarks, we tested out different types of commonly used queries. While ELK was better at performing queries like COUNT, SigNoz is 13x faster than ELK for aggregate queries. * Storage used by SigNoz for the same amount of logs is about half of what ELK uses. * Loki doesn't perform well if you want to index and query high cardinality data. In our setup for Loki we were not able to push it to ingest high cardinality labels/indexes. Version Info : * Logstash: 8.4.3 * Elasticsearch: 8.4.3 * Promtail:2.6.1 * Loki: 2.6.1 * Grafana: 9.2.1 * Signoz-otel-collector: 0.55.3 * Clickhouse-server: 22.4.5 --------------------------------------------------------------------- Note: We saw Loki team has recently shared some improvements in querying speed, but this benchmark is not updated based on this update and we have not verified if it would help in high cardinality data. If anyone in the community has been able to get good performance for high cardinality data, we would love to learn more. About Logs performance benchmark repo: Comparing Elastic, Loki and SigNoz signoz.io/blog/logs-performance-benchmark/ Topics benchmark performance logging Resources Readme Stars 52 stars Watchers 4 watching Forks 2 forks Contributors 2 * @nityanandagohain nityanandagohain Nityananda Gohain * @pranay01 pranay01 Pranay Prateek Languages * Shell 96.1% * Dockerfile 3.9% Footer (c) 2023 GitHub, Inc. Footer navigation * Terms * Privacy * Security * Status * Docs * Contact GitHub * Pricing * API * Training * Blog * About You can't perform that action at this time. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.