Rayhaan JaufeerallyandClaude Opus 5.5
361c48f656
A full table from several neighbors means millions of small, long-lived allocations that are replaced as routes change. jemalloc keeps the resident size of such a workload closer to what is in use than the system allocator does, glibc's in particular, and does not depend on the C library the binary is linked with. Not on MSVC, which jemalloc does not support. Building now needs a C compiler and make; the installation page says so. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
28 lines
687 B
TOML
28 lines
687 B
TOML
[package]
|
|
name = "bgp"
|
|
description = "A Border Gateway Protocol implementation"
|
|
authors.workspace = true
|
|
edition.workspace = true
|
|
homepage.workspace = true
|
|
license.workspace = true
|
|
repository.workspace = true
|
|
version.workspace = true
|
|
|
|
[dependencies]
|
|
bgp-server.workspace = true
|
|
bgp-web.workspace = true
|
|
clap.workspace = true
|
|
eyre.workspace = true
|
|
protobuf.workspace = true
|
|
tokio.workspace = true
|
|
tracing.workspace = true
|
|
tracing-subscriber.workspace = true
|
|
|
|
# jemalloc does not build with the MSVC toolchain; there the system
|
|
# allocator is used.
|
|
[target.'cfg(not(target_env = "msvc"))'.dependencies]
|
|
tikv-jemallocator.workspace = true
|
|
|
|
[lints]
|
|
workspace = true
|