Add VictoriaLogs results for c6a.4xlarge #286
Merged
+157
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
VictoriaLogs is a database for logs. It wasn't designed as analytical database, but it has been appeared that it provides enough functionality for ClickBench: it happily consumes hits.json via JSON lines data ingestion endpoint, and its' query language supports all the queries used in the ClickBench - see victorialogs/queries.logsql with all the queries translated into LogsQL ( https://docs.victoriametrics.com/victorialogs/logsql/ ). Fun fact - LogsQL queries are shorer than the corresponding SQL queries, and they are easier to read (YMMV) :) VictoriaLogs doesn't need any table schema, so victorialogs folder has no create.sql file. The resulting performance isn't so good comparing to ClickHouse, but there are a few queries, where VictoriaLogs provides better performance than ClickHouse because of bloom filters and "log streams" features. See https://docs.victoriametrics.com/victorialogs/keyconcepts/ . These features speed up "needle in the haystack" queries over large volumes of logs, which do not fit RAM, such as "search for logs with the given trace_id". Such queries are typical during logs' exploration.
rschu1ze
reviewed
Jan 17, 2025
…ptions passed to victorialogs executable
rschu1ze
reviewed
Jan 19, 2025
| "load_time": 1265, | ||
| "data_size": 17110607560, | ||
| "result": [ | ||
| [0.03, 0.013, 0.014], |
There was a problem hiding this comment.
Was able to reproduce the measurements locally.
rschu1ze
approved these changes
Jan 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
VictoriaLogs is a database for logs. It wasn't designed as analytical database, but it has been appeared that it provides enough functionality for ClickBench: it happily consumes hits.json via JSON lines data ingestion endpoint, and its' query language supports all the queries used in the ClickBench - see victorialogs/queries.logsql with all the queries translated into LogsQL ( https://docs.victoriametrics.com/victorialogs/logsql/ ). Fun fact - LogsQL queries are shorer than the corresponding SQL queries, and they are easier to read (YMMV) :)
VictoriaLogs doesn't need any table schema, so victorialogs folder has no create.sql file.
The resulting performance isn't so good comparing to ClickHouse, but there are a few queries, where VictoriaLogs provides better performance than ClickHouse because of bloom filters and "log streams" features. See https://docs.victoriametrics.com/victorialogs/keyconcepts/ . These features speed up "needle in the haystack" queries over large volumes of logs, which do not fit RAM, such as "search for logs with the given trace_id". Such queries are typical during logs' exploration.