Skip to content

Update throughput reference #383

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update throughput reference #383

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 10 additions & 21 deletions fern/api-reference/pricing-resources/resources/throughput.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,25 +6,19 @@
slug: reference/throughput
---

<Info>
Getting hit with rate limits?

[Talk to our team](https://www.alchemy.com/contact-sales) to increase your throughput.
</Info>

## What is throughput?

Throughput is a measure of the number of requests your application can send per second. It is often known as the applications "rate limit".

If a large number of requests are sent at the same time, you may hit your throughput capacity. However, under Alchemy's elastic throughput system, users are *guaranteed* their given throughput limit (measured in [compute units per second](/reference/throughput#scroll-what-are-compute-units-per-second-cups)), but will often experience higher throughput in practice.

In most instances, hitting your throughput limit will not affect your user's experience engaging with your application. As long as retries are implemented, the requests will go through in the following second. As a general rule of thumb, if you are experiencing **under 30%** rate limited requests, [using retries](/reference/throughput#retries) is the best solution.
Throughput refers to the volume of requests your app can successfully send to Alchemy's infrastructure within a given time frame — and is configured by throughput limits set for your account.

***

## Elastic Throughput
## How throughput at Alchemy works

<Check />
On Alchemy, throughput is defined in terms of CUPS (Compute Units Per Second), and throughput limits vary depending on account tier.

- Throughput is now set at the account level (no longer at the app level). This means limits apply to all your apps in aggregate.

Check warning on line 19 in fern/api-reference/pricing-resources/resources/throughput.mdx

View workflow job for this annotation

GitHub Actions / Lint Files 

Unexpected unordered list marker `-`, expected `*`
- The Throughput Page is where you can find your current account throughput and throughput limit. Enterprise customers can also use this page to set custom throughput overrides for specific apps.

Check warning on line 20 in fern/api-reference/pricing-resources/resources/throughput.mdx

View workflow job for this annotation

GitHub Actions / Lint Files 

Unexpected unordered list marker `-`, expected `*`
- Limits are evaluated over a 10s rolling window via a token bucket algorithm with strict refill rates. For example, Free tier customers with 500 CU/s throughput limit can access up to 5000 CU over a 10s period. This structure allows us to gracefully handle spikes in traffic.

Check warning on line 21 in fern/api-reference/pricing-resources/resources/throughput.mdx

View workflow job for this annotation

GitHub Actions / Lint Files 

Unexpected unordered list marker `-`, expected `*`

***

Expand Down Expand Up @@ -115,22 +109,17 @@

### Ethereum Goerli, Polygon Mumbai (and other testnets)

<Warning>
While you can use the Goerli testnet, we caution against it as the Ethereum Foundation has announced that [Goerli will soon be deprecated](https://www.alchemy.com/blog/goerli-faucet-deprecation).

We therefore recommend using [Sepolia](https://www.alchemy.com/overviews/sepolia-testnet) testnet as Alchemy has full Sepolia support and a free [Sepolia faucet](https://sepoliafaucet.com/) also.
</Warning>

#### HTTP

Check warning on line 113 in fern/api-reference/pricing-resources/resources/throughput.mdx

View workflow job for this annotation

GitHub Actions / Lint Files 

Unexpected `2` blank lines before node, expected up to `1` blank line, remove `1` blank line

[https://eth-goerli.g.alchemy.com/v2/AxnmGEYn7VDkC4KqfNSFbSW9pHFR7PDO](https://eth-goerli.g.alchemy.com/v2/AxnmGEYn7VDkC4KqfNSFbSW9pHFR7PDO)
[https://eth-sepolia.g.alchemy.com/v2/AxnmGEYn7VDkC4KqfNSFbSW9pHFR7PDO](https://eth-sepolia.g.alchemy.com/v2/AxnmGEYn7VDkC4KqfNSFbSW9pHFR7PDO)

#### WebSocket

[\<wss://eth-goerli.g.alchemy.com/v2/AxnmGEYn7VDkC4KqfNSFbSW9pHFR7PDO>]()
[\<wss://eth-sepolia.g.alchemy.com/v2/AxnmGEYn7VDkC4KqfNSFbSW9pHFR7PDO>]()

***

## Final Tips

Use a different key for each part of your project (e.g., frontend, backend, development) to isolate throughput usage to each use case. This also splits monitoring across different parts of your project, making it easier to debug issues and monitor usage.
Reach out to [email protected] with any questions you have!