feat: add log-benchmark stuff for blog #36
Closed
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
shuiyisong
commented
Aug 21, 2024
| @@ -0,0 +1,32 @@ | |||
| # Log benchmark comparison for GreptimeDB | |||
| This repo holds the configuration we used to benchmark GreptimeDB, Clickhouse and Elastic Search. | |||
There was a problem hiding this comment.
TODO: add link for en and ch blogs
shuiyisong
commented
Aug 21, 2024
| 4. When data insertion is finished, run queries against each database. Note: you'll need to update timerange value after data insertion. | ||
|
|
||
| ## Addition | ||
| - You can tune GreptimeDB's configuration to get better performance. |
There was a problem hiding this comment.
TODO: add link for performance tuning blog
sunng87
reviewed
Aug 21, 2024
|
duplicate of GreptimeTeam/greptimedb#4597 |
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.
No description provided.