From 728efa83980ca45a5256183803b20d5607699fd1 Mon Sep 17 00:00:00 2001 From: Shane Myrick Date: Wed, 5 Feb 2025 11:24:57 -0800 Subject: [PATCH 1/4] Update query-batching with billable details --- docs/source/routing/performance/query-batching.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/source/routing/performance/query-batching.mdx b/docs/source/routing/performance/query-batching.mdx index 50530f8797..e10d72b9d2 100644 --- a/docs/source/routing/performance/query-batching.mdx +++ b/docs/source/routing/performance/query-batching.mdx @@ -191,6 +191,9 @@ To enable batching in an Apollo client, configure `BatchHttpLink`. For details o If the router receives a query batch from a client, and batching is *not* enabled, the router sends a `BATCHING_NOT_ENABLED` error to the client. +## Query Batching and Paid Plans +When processing batched operations, the Router will count each entry in the batch as a distinct billable operation that counts towards your graph usage. Even if you send a batch with `N` requests of the same exact operation, that is counted the same as sending `N` of the same non-batched requests. Note that billable plans only track Router operations, so configuring subgraph batching does not impact your graph usage count. + ## Metrics for query batching Metrics in the GraphOS Router for query batching: From ef8438afd06db81a89895594bf10cd6fc3f4bbd1 Mon Sep 17 00:00:00 2001 From: Shane Myrick Date: Wed, 5 Feb 2025 11:27:30 -0800 Subject: [PATCH 2/4] Update query-batching.mdx --- docs/source/routing/performance/query-batching.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/source/routing/performance/query-batching.mdx b/docs/source/routing/performance/query-batching.mdx index e10d72b9d2..c4c41aaaea 100644 --- a/docs/source/routing/performance/query-batching.mdx +++ b/docs/source/routing/performance/query-batching.mdx @@ -191,8 +191,8 @@ To enable batching in an Apollo client, configure `BatchHttpLink`. For details o If the router receives a query batch from a client, and batching is *not* enabled, the router sends a `BATCHING_NOT_ENABLED` error to the client. -## Query Batching and Paid Plans -When processing batched operations, the Router will count each entry in the batch as a distinct billable operation that counts towards your graph usage. Even if you send a batch with `N` requests of the same exact operation, that is counted the same as sending `N` of the same non-batched requests. Note that billable plans only track Router operations, so configuring subgraph batching does not impact your graph usage count. +## Query Batching and GraphOS Plans +When processing batched operations, the Router will count each entry in the batch as a distinct billable operation that counts towards your graph usage. Even if you send a batch with `N` requests of the same exact operation, that is counted the same as sending `N` requests of the same non-batched operation. Note that GraphOS plans only track Router operations, so configuring subgraph batching does not impact your graph usage count. ## Metrics for query batching From d6f60f7bfec42d01921f4f83fc60cf3c043522b0 Mon Sep 17 00:00:00 2001 From: Shane Myrick Date: Wed, 5 Feb 2025 11:29:30 -0800 Subject: [PATCH 3/4] Update query-batching.mdx --- docs/source/routing/performance/query-batching.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/routing/performance/query-batching.mdx b/docs/source/routing/performance/query-batching.mdx index c4c41aaaea..64d6169002 100644 --- a/docs/source/routing/performance/query-batching.mdx +++ b/docs/source/routing/performance/query-batching.mdx @@ -192,7 +192,7 @@ To enable batching in an Apollo client, configure `BatchHttpLink`. For details o If the router receives a query batch from a client, and batching is *not* enabled, the router sends a `BATCHING_NOT_ENABLED` error to the client. ## Query Batching and GraphOS Plans -When processing batched operations, the Router will count each entry in the batch as a distinct billable operation that counts towards your graph usage. Even if you send a batch with `N` requests of the same exact operation, that is counted the same as sending `N` requests of the same non-batched operation. Note that GraphOS plans only track Router operations, so configuring subgraph batching does not impact your graph usage count. +When processing batched operations, the Router will count each entry in the batch as a distinct billable operation that counts towards your graph usage. Even if you send a batch with size `N` of operations, that is counted the same as sending `N` requests of the same non-batched operation. Note that GraphOS plans only track Router operations, so configuring subgraph batching does not impact your graph usage count. ## Metrics for query batching From de906f2f2cec3930268f4f0d13be758fa44a6d9e Mon Sep 17 00:00:00 2001 From: Shane Myrick Date: Wed, 5 Feb 2025 11:51:37 -0800 Subject: [PATCH 4/4] Update docs/source/routing/performance/query-batching.mdx Co-authored-by: Edward Huang --- docs/source/routing/performance/query-batching.mdx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/source/routing/performance/query-batching.mdx b/docs/source/routing/performance/query-batching.mdx index 64d6169002..e320826a81 100644 --- a/docs/source/routing/performance/query-batching.mdx +++ b/docs/source/routing/performance/query-batching.mdx @@ -191,8 +191,10 @@ To enable batching in an Apollo client, configure `BatchHttpLink`. For details o If the router receives a query batch from a client, and batching is *not* enabled, the router sends a `BATCHING_NOT_ENABLED` error to the client. -## Query Batching and GraphOS Plans -When processing batched operations, the Router will count each entry in the batch as a distinct billable operation that counts towards your graph usage. Even if you send a batch with size `N` of operations, that is counted the same as sending `N` requests of the same non-batched operation. Note that GraphOS plans only track Router operations, so configuring subgraph batching does not impact your graph usage count. +## Query batching and GraphOS plans +When processing batched operations, the router counts each entry in the batch as a distinct billable operation that counts towards your graph usage. Sending a batch with `N` operations is counted the same as sending `N` requests of the same non-batched operation. + +Note that GraphOS plans only track router operations, so configuring subgraph batching does not impact your graph usage count. ## Metrics for query batching