TigerGraph · Rate Limits

Tigergraph Rate Limits

The TigerGraph REST++ API does not publish fixed per-second request quotas; throughput is governed by the database server's configuration and the size of the deployed workspace. REST++ exposes RESTPP.Factor.DefaultQueryTimeout (the GSQL.QUERY timeout) and a configurable maximum response buffer/result size, and concurrent query execution is bounded by the workspace's CPU and memory. On TigerGraph Savanna, effective throughput scales with the chosen workspace size, and customer level (Free, Paid, Premium, Enterprise) governs workspace count and resource quotas. Specific numeric limits are not reconciled here.

Tigergraph Rate Limits is the machine-readable rate-limit profile for TigerGraph on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring seconds, bytes, queries, and workspaces.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Graph Database, Analytics, GSQL, REST++, and Graph Analytics.

4 Limits Throttle: 503
Graph DatabaseAnalyticsGSQLREST++Graph AnalyticsRate LimitingQuotasThrottling

Limits

Query Timeout query
seconds
see provider documentation
Governed by DefaultQueryTimeout / overridable per-request via the GSQL-TIMEOUT header.
Response Size request
bytes
see provider documentation
Maximum REST++ response buffer / result size is server-configurable.
Concurrent Queries workspace
queries
see provider documentation
Bounded by workspace CPU/memory; scales with TigerGraph Savanna workspace size.
Workspace Quota account
workspaces
1 R/W + 2 read-only (Free tier)
Raised at Paid, Premium, and Enterprise customer levels.

Policies

Tiered Quotas
Workspace count and resource quotas increase across Free, Paid, Premium, and Enterprise customer levels on Savanna.
Backoff Strategy
Clients should implement exponential backoff with jitter and retry on transient 503 / connection errors.

Sources