mirror of
https://github.com/neondatabase/neon.git
synced 2026-06-04 22:10:39 +00:00
024109fbeb
We currently have a semaphore based rate limiter which we hope will keep us under S3 limits. However, the semaphore does not consider time, so I've been hesitant to raise the concurrency limit of 100. See #3698. The PR Introduces a leaky-bucket based rate limiter instead of the `tokio::sync::Semaphore` which will allow us to raise the limit later on. The configuration changes are not contained here.
33 lines
814 B
TOML
33 lines
814 B
TOML
[package]
|
|
name = "remote_storage"
|
|
version = "0.1.0"
|
|
edition.workspace = true
|
|
license.workspace = true
|
|
|
|
[dependencies]
|
|
anyhow.workspace = true
|
|
async-trait.workspace = true
|
|
once_cell.workspace = true
|
|
aws-smithy-http.workspace = true
|
|
aws-types.workspace = true
|
|
aws-config.workspace = true
|
|
aws-sdk-s3.workspace = true
|
|
aws-credential-types.workspace = true
|
|
hyper = { workspace = true, features = ["stream"] }
|
|
serde.workspace = true
|
|
serde_json.workspace = true
|
|
tokio = { workspace = true, features = ["sync", "fs", "io-util"] }
|
|
tokio-util.workspace = true
|
|
toml_edit.workspace = true
|
|
tracing.workspace = true
|
|
metrics.workspace = true
|
|
utils.workspace = true
|
|
pin-project-lite.workspace = true
|
|
workspace_hack.workspace = true
|
|
|
|
leaky-bucket = "1.0"
|
|
|
|
[dev-dependencies]
|
|
tempfile.workspace = true
|
|
test-context.workspace = true
|