examples(latency): Add example to calculate client and server latency. #50
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.
This is for CLOUD-260.
This adds an example to get the client-side and the server-side latency of a query.
The important bit is the following snippet:
dgraph-js-http/examples/latency/index-async-await.js
Lines 112 to 115 in 88ffe94
Client-side latency is calculated using
console.time
andconsole.timeEnd
around a query call to capture the client-side latency.Server-side latency is calculated by Dgraph itself. This example prints it out from the query response
res.extensions.server_latency
.Example command and output:
The following flags are available in this example:
--addr
: The Dgraph address. Can be a Dgraph Cloud endpoint following the instructions: https://github.com/dgraph-io/dgraph-js-http#create-a-client-for-dgraph-cloud-endpoint. Defaults tohttp://localhost:8080
.--api-key
: The Dgraph Cloud API Key. Required if the--addr
is a Dgraph Cloud endpoint.--drop-all
: Call DropAll on Dgraph before loading the data for this example.This change is