web3-proxy/Cargo.toml

[workspace]
members = [
  "deduped_broadcast",
  "deferred-rate-limiter",
  "entities",
  "latency",
  "migration",
  "payment-contracts",
  "rate-counter",
  "redis-rate-limiter",
  "web3_proxy",
  "web3_proxy_cli",
]
resolver = "2"

[profile.release]
# `debug = true` so that sentry can give us line numbers
debug = true

[profile.faster_release]
inherits = "release"

# spend longer compiling for a faster binary
codegen-units = 1
# `link time optimization = true = fat`
lto = true
first pass at caching i'm confused. i had it over 100k connections on friday, but now even when i go back to those commits, i can't get that high 2022-05-05 22:06:03 +03:00			`[workspace]`
			`members = [`
Deduped broadcast channel (#209) * upgrade and start adding deduped_broadcast * basic test * accept arg for cache ttl * first pass at bringing the tx firehose back * try_send instead of send since there aren't always receivers * deduped broadcaster needs the try send * track counts and include in /status * use config for enable subscribe_txs 2023-09-13 22:05:47 +03:00			`"deduped_broadcast",`
work in progress 2022-09-15 20:57:24 +03:00			`"deferred-rate-limiter",`
setup database and stub migrations 2022-07-26 07:53:38 +03:00			`"entities",`
Peak ewma (#63) * use peak-ewma instead of head for latency calculation * Implement some suggested changes from PR * move latency to new package in workspace root * fix unit tests which now require peak_latency on Web3Rpc * Switch to atomics for peak-ewma This change is to avoid locking from tokio::sync::watch. * add decay calculation to latency reads in peak-ewma * Add some tests for peak-ewma * Sensible latency defaults and not blocking on full * Cleanup and a couple additional comments 2023-05-11 23:09:15 +03:00			`"latency",`
drop redis-cell in favor of simpler query 2022-08-16 01:50:56 +03:00			`"migration",`
use MultiAbigen 2023-05-31 21:52:51 +03:00			`"payment-contracts",`
add simple rate-counter 2023-02-26 01:40:22 +03:00			`"rate-counter",`
work in progress 2022-09-15 20:57:24 +03:00			`"redis-rate-limiter",`
fix directory structure 2022-08-05 22:22:23 +03:00			`"web3_proxy",`
split command line into separte module 2023-08-03 10:16:54 +03:00			`"web3_proxy_cli",`
first pass at caching i'm confused. i had it over 100k connections on friday, but now even when i go back to those commits, i can't get that high 2022-05-05 22:06:03 +03:00			`]`
set resolver version 2023-06-12 21:02:45 +03:00			`resolver = "2"`
make it maybe faster 2022-05-13 10:05:38 +03:00
optional tracing-sentry 2022-10-25 00:07:29 +03:00			`[profile.release]`
codegen-units = 1 2023-01-27 06:23:52 +03:00			# `debug = true` so that sentry can give us line numbers
optional tracing-sentry 2022-10-25 00:07:29 +03:00			`debug = true`
make a new profile for codegen-units = 1 2023-02-03 00:55:48 +03:00
			`[profile.faster_release]`
			`inherits = "release"`

sccache for builds 2023-07-28 20:43:02 +03:00			`# spend longer compiling for a faster binary`
codegen-units = 1 2023-01-27 06:23:52 +03:00			`codegen-units = 1`
move lto to faster_release provile 2023-07-28 22:17:20 +03:00			# `link time optimization = true = fat`
			`lto = true`