-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix schema on getting started page; Extract tagline #15
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,7 +7,8 @@ github_url: https://github.com/block/elasticgraph | |
x_url: https://x.com/elasticgraph | ||
x_username: "@ElasticGraph" | ||
support_email: [email protected] | ||
description: ElasticGraph is an open-source framework for indexing, searching, grouping, and aggregating data | ||
tagline: Schema-driven, scalable, cloud-native, batteries-included GraphQL with superpowers. | ||
description: ElasticGraph is an open-source framework for indexing, searching, grouping, and aggregating data. | ||
|
||
|
||
# Reusable CSS styling for the site, available via the `site.style` variable, ex: `{{ site.style.body }}` | ||
|
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of putting this as one metric here under dataset, can we put separate QPS metrics under the query card (and call it
Query Performance
instead ofQuery Latency
) and put the indexing QPS on the ingestion card and call itIngestion Performance
orIndexing Latency
?And then we can put more accurate numbers for them.
> 500 QPS
for query performance (I just checked, and we regularly go over that in one cluster)> 180K documents per second
for ingestion/indexing performance (our last backfill hovered between 180K and 200K documents per second!)100 documents per second of indexing perf isn't that impressive so it's nice to put more accurate numbers here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also can we add something about availability? e.g.
> 99.999% Availability
(which is usually our low water mark in a given week...).