perf(build): Option to use precompiled RocksDB. Isolate spurious debug crates from release #1509

gamesguru · 2026-03-08T10:54:47Z

gamesguru commented

2026-03-08 10:54:47 +00:00

This PR places heavy debug libraries like tracing-flame BEHIND debug feature flags.

I have also documented the benefits of pre-compiling RocksDB (see below), which requires exposing the ROCKSDB_LIB_DIR env var.

Net result is a beefed up build process, or perhaps leaned down?
It won't cure the deadlocks in our runtime, but at least now we can compile in under 3 minutes ~~and~~ or on 512 MB of ram (realistically probably not both at once!).

This doesn't really help docker-in-docker, since you'd need to compile RustDB every CI run. But I think we may be able to find a docker image which supports the same major and minor version of the RocksDB headers, which would replace building a million lines of code with downloading 150 MB of binaries over enterprise-grade Ethernet.

git clone https://forgejo.ellis.link/continuwuation/rust-rocksdb-zaidoon1.git
cd rust-rocksdb-zaidoon1
git checkout 61d9d23872197e9ace4a477f2617d5c9f50ecb23
git submodule update --init --recursive
cd librocksdb-sys/rocksdb
make shared_lib -j$(nproc)
sudo make install-shared INSTALL_PATH=/usr/local
sudo ldconfig
# you must do this where your tools (i.e., make, engage, or just) will see it
export ROCKSDB_LIB_DIR=/usr/local/lib

Pull request checklist:

This pull request targets the main branch, and the branch is named something other than
main.
I have written an appropriate pull request title and my description is clear.
I understand I am responsible for the contents of this pull request.
I have followed the contributing guidelines:
- My contribution follows the code style, if applicable.
- I ran pre-commit checks before opening/drafting this pull request.
- I have tested my contribution (or proof-read it for documentation-only changes)
  myself, if applicable. This includes ensuring code compiles.
- My commit messages follow the commit message format and are descriptive.
- I have written a news fragment for this PR, if applicable.

This PR places heavy debug libraries like `tracing-flame` BEHIND debug feature flags. I have also documented the benefits of **pre-compiling RocksDB** (see below), which requires exposing the `ROCKSDB_LIB_DIR` env var. Net result is a beefed up build process, or perhaps leaned down? It won't cure the deadlocks in our runtime, but at least now we can compile in under 3 minutes ~~and~~ or on 512 MB of ram (realistically probably not both at once!). This doesn't really help docker-in-docker, since you'd need to compile RustDB every CI run. But I think we may be able to find a docker image which supports the same major and minor version of the RocksDB headers, which would replace building a million lines of code with downloading 150 MB of binaries over enterprise-grade Ethernet. ```shell git clone https://forgejo.ellis.link/continuwuation/rust-rocksdb-zaidoon1.git cd rust-rocksdb-zaidoon1 git checkout 61d9d23872197e9ace4a477f2617d5c9f50ecb23 git submodule update --init --recursive cd librocksdb-sys/rocksdb make shared_lib -j$(nproc) sudo make install-shared INSTALL_PATH=/usr/local sudo ldconfig # you must do this where your tools (i.e., make, engage, or just) will see it export ROCKSDB_LIB_DIR=/usr/local/lib ```     **Pull request checklist:**  - [x] This pull request targets the `main` branch, and the branch is named something other than `main`. - [x] I have written an appropriate pull request title and my description is clear. - [x] I understand I am responsible for the contents of this pull request. - I have followed the [contributing guidelines][c1]: - [x] My contribution follows the [code style][c2], if applicable. - [x] I ran [pre-commit checks][c1pc] before opening/drafting this pull request. - [ ] I have [tested my contribution][c1t] (or proof-read it for documentation-only changes) myself, if applicable. This includes ensuring code compiles. - [x] My commit messages follow the [commit message format][c1cm] and are descriptive. - [ ] I have written a [news fragment][n1] for this PR, if applicable.  [c1]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md [c2]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/docs/development/code_style.mdx [c1pc]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#pre-commit-checks [c1t]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#running-tests-locally [c1cm]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#commit-messages [n1]: https://towncrier.readthedocs.io/en/stable/tutorial.html#creating-news-fragments

gamesguru added 5 commits

2026-03-08 10:54:47 +00:00

perf(build): isolate tracing-flame from release builds, along with other heavy deps 6216f3dc55

fixup makefile (missing ROCKSDB_LIB_DIR=/usr/lib in one spot) b0ffc27bfc

wip: isolate some open telemetry behind feature flags 55ffd8bf00

lint/compile errors due to using library system packages 7a47720398

build(perf): document benefits of pre-compiling rocksdb:

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

a241fde347

git clone https://forgejo.ellis.link/continuwuation/rust-rocksdb-zaidoon1.git
    cd rust-rocksdb-zaidoon1
    git checkout 61d9d23872197e9ace4a477f2617d5c9f50ecb23
    git submodule update --init --recursive
    cd librocksdb-sys/rocksdb
    make shared_lib -j$(nproc)
    sudo make install-shared INSTALL_PATH=/usr/local
    sudo ldconfig

Jade reviewed

2026-03-08 10:56:49 +00:00

src/main/Cargo.toml Outdated

					
				@ -59,16 +59,18 @@ standard = [

					"systemd",

					"url_preview",

					"zstd_compression",

				    "sentry_telemetry",

Why disable sentry and opentelemetry?

(I use both of these in prod, as do others)

typically telemetry is opt-in

you guys will have to figure out what this means for your release process

typically telemetry is opt-in you guys will have to figure out what this means for your release process

This is a misunderstanding of what these options do.

@gamesguru

The telemetry here is opt-in via configuration. Asking end users to recompile continuwuity themselves for observability features seems a little odd, when these features are documented. I'd expect to have to compile a version without them, if I particularly wanted them gone.

Unless you're suggesting they add another build to the release pipeline with the telemetry features compiled in, which would double the current builds, this seems odd.

@gamesguru The telemetry here is opt-in via configuration. Asking end users to recompile continuwuity themselves for observability features seems a little odd, when these features are documented. I'd expect to have to compile a version without them, if I particularly wanted them gone. Unless you're suggesting they add another build to the release pipeline with the telemetry features compiled in, which would double the current builds, this seems odd.

What i mean is that should be configured as part of the release. I am perfectly okay with you passing the telemetry flag in with every action, workflow, runner, or prod build agent you think needs it.

But i don't think it's appropriate that this should be hard-coded in the rust configurations. I don't think someone compiling from source should be forced or automatically opted-into telemetry unless they have the expertise or time to reverse engineer and modify our rust code's build process. We should allow people who wish to compile their own source the option to disable it.

I'm not even sure if rust supports enablement by default for certain flags? I'm even even okay with enabling the flag by default.

What I'm resisting is the idea that the flag shouldn't exist at all, or there shouldn't be an option to disable the feature.

What i mean is that should be configured as part of the release. I am perfectly okay with you passing the telemetry flag in with every action, workflow, runner, or prod build agent you think needs it. But i don't think it's appropriate that this should be hard-coded in the rust configurations. I don't think someone compiling from source should be *forced* or automatically opted-into telemetry unless they have the expertise or time to reverse engineer and modify our rust code's build process. We should allow people who wish to compile their own source the option to disable it. I'm not even sure if rust supports enablement by default for certain flags? I'm even even okay with enabling the flag by default. What I'm resisting is the idea that the flag shouldn't exist at all, or there shouldn't be an option to disable the feature.

I'm not sure what you mean by there's no option to disable the feature. You can select features when you compile. --no-default-features --features "x y z" will only include features x, y, and z. I feel like that's not what you meant, but I can't tell what else you could be talking about, so do correct me if I'm wrong.

Also, "enablement by default for certain flags"? It's done by default right now. That's what the default feature set is. None of this is forced upon people compiling from source or set in stone.

To clarify, the situation is currently that observability features are compiled in by default, but you always have the option to compile continuwuity without them.

I apologise, but I'm very confused.

I'm not sure what you mean by there's no option to disable the feature. You can select features when you compile. `--no-default-features --features "x y z"` will only include features `x`, `y`, and `z`. I feel like that's not what you meant, but I can't tell what else you could be talking about, so do correct me if I'm wrong. Also, "enablement by default for certain flags"? It's done by default right now. That's what the default feature set is. None of this is forced upon people compiling from source or set in stone. To clarify, the situation is currently that observability features are compiled in by default, but you always have the option to compile continuwuity without them. I apologise, but I'm very confused.

for example cargo build --features full,otlp_telemetry --profile release will after this PR accomplish exactly the same as the old default behavior that you're used to.

i admittedly did not have time to document things in all the relevant places that may be affected. I am going to lean on the team a bit to help fill in those gaps and make sure this gets laid out as effectively and clearly as we can

for example `cargo build --features full,otlp_telemetry --profile release` will after this PR accomplish exactly the same as the old default behavior that you're used to. i admittedly did not have time to document things in all the relevant places that may be affected. I am going to lean on the team a bit to help fill in those gaps and make sure this gets laid out as effectively and clearly as we can

ok so, even if you use the --no-default-features (today on main), it looks like it skips the runtime but still was compiling the crates.

and that's really what this PR is about, cutting build times drastically and making caching of our largest dependency, which has stayed at the same version for a while, trivially easy.

if it's too confusing what to do now about telemetry, we need to figure out some ideas there

ok so, even if you use the `--no-default-features` (today on `main`), it looks like it skips the runtime but still was compiling the crates. and that's really what this PR is about, cutting build times drastically and making caching of our largest dependency, which has stayed at the same version for a while, trivially easy. if it's too confusing what to do now about telemetry, we need to figure out some ideas there

plus, even if it no-ops the runtime... a open-source project like ours should probably exclude the telemetry SDK from the build by default

I think the confusion here comes from the term "telemetry" when it is actually for monitoring and health checks, which are incredibly useful and normal features for production server software to have. Caddy, for example, comes with similar features built in.

If you want to omit them by default, that feels like it should be a separate PR.

I think the confusion here comes from the term "telemetry" when it is actually for monitoring and health checks, which are incredibly useful and normal features for production server software to have. Caddy, for example, comes with similar features built in. If you want to omit them by default, that feels like it should be a separate PR.

Some of what I said was wrong and you were right that --no-default-features works the same as this branch. But that seems like a bit obscure of a flag, and by default a LOT more is included, i.e., I'm not sure what tracing-flame is but it's 2nd slowest for me after RocksDB, and this PR cuts it out by default. I just monitor with journalctl and sar. Feels like we can maybe revisit adding flag(s) for 3rd party library inclusion. I noticed the anti spam is included even with no-default. I don't use any of the "plugins" so I can't say how they're best organized behind feature flags. And I need to look a bit more how they're connected and the binary size and compile times they add.

What is the difference then with full and default?

I guess in the interests of getting this thru I will revert that part for now, since you told me about the no default features flag. That should speed my builds up on its own 👍

Some of what I said was wrong and you were right that `--no-default-features` works the same as this branch. But that seems like a bit obscure of a flag, and by default a LOT more is included, i.e., I'm not sure what `tracing-flame` is but it's 2nd slowest for me after RocksDB, and this PR cuts it out by default. I just monitor with `journalctl` and `sar`. Feels like we can maybe revisit adding flag(s) for 3rd party library inclusion. I noticed the anti spam is included even with no-default. I don't use any of the "plugins" so I can't say how they're best organized behind feature flags. And I need to look a bit more how they're connected and the binary size and compile times they add. What is the difference then with full and default? I guess in the interests of getting this thru I will revert that part for now, since you told me about the no default features flag. That should speed my builds up on its own 👍

gamesguru added 1 commit

2026-03-09 01:30:52 +00:00

build(docs): old compilers may need: CXXFLAGS="-Wno-error=unused-parameter"

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

1a6e84c0fc

gamesguru added 1 commit

2026-03-09 09:52:31 +00:00

update env vars defs for building. see below note on DISABLE_JEMALLOC=1,

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

594b39080e

```shell
git clone https://forgejo.ellis.link/continuwuation/rust-rocksdb-zaidoon1.git
cd rust-rocksdb-zaidoon1
git checkout 61d9d23872197e9ace4a477f2617d5c9f50ecb23
git submodule update --init --recursive
cd librocksdb-sys/rocksdb
PORTABLE=0 DISABLE_JEMALLOC=1 CXXFLAGS="-Wno-error=unused-parameter" make shared_lib -j$(nproc)
sudo make install-shared INSTALL_PATH=/usr/local
sudo ldconfig
```

nex added the

Enhancement

label

2026-03-09 16:06:42 +00:00

nex changed title from ~~Build(perf): Option to use precompiled RocksDB. Isolate spurious debug crates from release~~ to perf(build): Option to use precompiled RocksDB. Isolate spurious debug crates from release

2026-03-09 16:06:59 +00:00

gamesguru added 6 commits

2026-03-10 05:48:47 +00:00

Merge remote-tracking branch 'origin/main' into guru/perf/build-optimizations-dep-tree 4112661e61

update d991d71299

build: prelim support for bindgen, bundling the RocksDB assembly into standalone Rust binaries 605a56e8ec

revised commands to build rocksdb static assembly:

```shell
DISABLE_JEMALLOC=1 EXTRA_CXXFLAGS="-Wno-error=unused-parameter" make shared_lib static_lib -j$(nproc)
sudo make install-shared INSTALL_PATH=/usr/local
sudo make install-static INSTALL_PATH=/usr/local
sudo ldconfig
```

more edits, but both are working fine 110af0f227

build: back to mt_static apparently, demands RustRover b76ae4141a

document tech debt: wasteful presence DB i/o and a need for LRU caching

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

2a2c513205

gamesguru added 1 commit

2026-03-10 07:04:40 +00:00

leaner runtime 560 crates. take tracers out of default features. give the people choice

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

9e76153ac0

42 megabytes. 8 minutes. release-max-perf.

we need to improve our documentation, so admins understand how to get non-default features.

i suspect nothing additional is needed to run the full Complement Test suite and serve all basic homeserver functions.

not even URL preview zero overhead: extreme cases may leak IPs or allow forgery attacks.
there's no harm in recompiling once you find you want it.

testing: add WIP engage target for complement tests (not everyone has buildkit or buildx)

gamesguru added 1 commit

2026-03-11 03:26:01 +00:00

add cargo config to use mold, faster linker than ld or cc

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

9f6fd04507

this should also apply to RustRover by default, and you will notice less redundant rebuilding of built static imports.

gamesguru added 1 commit

2026-03-11 03:38:40 +00:00

direnv auto-detect sccache, faster builds from CLI

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

2fa147c9ec

gamesguru added 1 commit

2026-03-11 03:48:44 +00:00

add redundant config since RustRover has the IQ of a carrot. TODO: prevent this breaking if sccache or mold aren't found

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

e9ec975f03

gamesguru added 1 commit

2026-03-11 04:03:13 +00:00

RustRover default to prebuilt RocksDB if found in/usr/local

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

f767a1174d

gamesguru added 1 commit

2026-03-11 04:18:46 +00:00

help RustRover see. You may need below commands. And i may nest things eventually in /usr/loca/uwu for isolation.

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

78e24ffc48

This will tell your linker to look in `/usr/local`, but it may also cause conflicts or unexpected behavior:

```bash
echo "/usr/local/lib" | sudo tee /etc/ld.so.conf.d/usr-local.conf
sudo ldconfig
```

gamesguru added 1 commit

2026-03-11 04:23:08 +00:00

add docs on debugging over SSH with gdb or RustRover

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

b5565021e9

gamesguru force-pushed guru/perf/build-optimizations-dep-tree from b5565021e9

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

to 33d71edec2

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

2026-03-11 04:36:11 +00:00

Compare

gamesguru added 1 commit

2026-03-11 04:49:12 +00:00

add a proof of concept justfile for profiling cpu/mem usage and heat maps

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

7c61c8e09a

gamesguru added 1 commit

2026-03-11 05:32:46 +00:00

justfile targets to prebuild jemalloc, lz4, rocksdb, and zstd. down to 553 crates.

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

2b66ae9ad0

gamesguru added 1 commit

2026-03-11 05:54:29 +00:00

cargo configs so RustRover uses prebuilt libraries

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

d6ab95705a

gamesguru added 1 commit

2026-03-11 06:00:10 +00:00

update "debugging over SSH" docs to use rust-gdb

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

2ec6cafaa3

gamesguru added 1 commit

2026-03-11 06:27:26 +00:00

TODO: investigate dep. inversion w/ ruma, since it rebuilds on trivial/unrelated changes it shouldn't. [empty-commit]

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

40f9517824

gamesguru added 1 commit

2026-03-11 06:42:16 +00:00

gitignore the .tmp/ in case not everyone echoed a gitignore in it with '**'

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

9422b5f761

gamesguru added 1 commit

2026-03-11 12:31:32 +00:00

add some build/compile profiling targets to justfile

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

714fdec98d

gamesguru added 1 commit

2026-03-11 17:21:31 +00:00

update justfile targets (fix). format files/whitespace.

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

bc90eb5e19

gamesguru added 1 commit

2026-03-11 18:34:53 +00:00

prune makefile from this branch

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

a6d377f8d1

gamesguru added 10 commits

2026-03-12 01:11:38 +00:00

Merge remote-tracking branch 'origin/main' into guru/perf/build-optimizations-dep-tree febd2881f1

git: 3-way patch from upstream, see: 5800d3c677

from this branch (origin is Jade's, github is mine), I ran:

```shell
FILES=$(gds origin/main --name-only)
BASE=$(git merge-base HEAD github/main)
git diff $BASE..github/main  -- $FILES | git apply --3way
```

fix bad 3-way merge b74600e490

restore presence/mod.rs to origin/main except comments on this branch ee8b4a25eb

seems linking is slow since adding mt_static (bad for devs) [empty-commit] 0ee24c7be4

wip 60b598c620

wip 2ec113ea99

fix d85c889b09

lint: wrap url_preview in feature config flag d7b975fb2c

prune makefile; fix my stupid slowdowns/regressions, but not quite as good as 9e76153a nor even a6d377f8 yet again.

Documentation / Build and Deploy Documentation (pull_request) Has been cancelled

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled

Details

Update flake hashes / update-flake-hashes (pull_request) Has been cancelled

Details

820f1d5d1f

gamesguru added 9 commits

2026-03-14 19:00:01 +00:00

build: add snappy explicitly under rocksdb 38b48d32f0

wip: idk snappy justfile stuff? 300be31e5f

add additional core deps to justfile prebuild 9fdcf9a889

simplify just target for jemalloc, fix to v5.3.0 4a290c9848

simplify just targets, go back to /usr/local/build e0bb2b3f42

tab completion? a67e86cf73

tweak justfile 0721163df0

fix: justfile for snappy cmake error f4407284d2

tidy/arrange justfile fix rockdb glitch

Documentation / Build and Deploy Documentation (pull_request) Blocked by required conditions

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Blocked by required conditions

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Blocked by required conditions

Details

Update flake hashes / update-flake-hashes (pull_request) Blocked by required conditions

Details

497dbf9164

gamesguru commented

2026-03-14 19:31:35 +00:00

Guys, I think what i'm gonna do here is open another PR that makes non-breaking, emergency changes that by default will use the following tools (if installed and available). But this new PR will otherwise change nothing about --features stuff and things that might completely break DevOps pipelines and require a bit more collaboration and thinking things through.

So my new PR will configure at the project level, i.e., thru cargo not direnv or anything else shell-level based that has a tendency to not be picked up by my cron jobs and five other tools on 3 different machines.

mold
clang (think we do this already)
sccache
pre-built/pre-installed: rocksdb, jemalloc, snappy, zstd, lz4, bzip2, and liburing

The feature flag changes are less important to me.

My laptop and poor VPS simply cannot handle building RocksDB concurrently with the rust project, and they benefit too immensely from these speedups as to neglect expediency here on my part.

I'm not able to quickly build my PRs without first merging this branch (which contains other changes in src/ and therefore arguably pollutes my tests of the PRs).

Guys, I think what i'm gonna do here is open another PR that makes non-breaking, emergency changes that by default will use the following tools (if installed and available). But this new PR will otherwise change nothing about `--features` stuff and things that might completely break DevOps pipelines and require a bit more collaboration and thinking things through. So my new PR will configure at the project level, i.e., thru `cargo` not `direnv` or anything else shell-level based that has a tendency to not be picked up by my `cron` jobs and five other tools on 3 different machines. - `mold` - `clang` (think we do this already) - `sccache` - pre-built/pre-installed: `rocksdb, jemalloc, snappy, zstd, lz4, bzip2, and liburing` The feature flag changes are less important to me. My laptop and poor VPS simply cannot handle building RocksDB concurrently with the rust project, and they benefit too immensely from these speedups as to neglect expediency here on my part. I'm not able to quickly build my PRs without first merging this branch (which contains other changes in `src/` and therefore arguably pollutes my tests of the PRs).