Repository navigation
Remove the on demand database backup and database.data_store - #1041
Merged
Merged
Conversation
epompeii
added this pull request to stack #1042
September 18, 2026 06:48
Contributor
|
| Project | Bencher |
| Branch | u/ep/s3-r2/server-backup |
| Testbed | intel-v1 |
Click to view all benchmark results
| Benchmark | Latency | Benchmark Result microseconds (碌s) (Result 螖%) | Upper Boundary microseconds (碌s) (Limit %) |
|---|---|---|---|
| Adapter::Json | 馃搱 view plot 馃毞 view threshold | 5.33 碌s(+5.48%)Baseline: 5.05 碌s | 6.16 碌s (86.49%) |
| Adapter::Magic (JSON) | 馃搱 view plot 馃毞 view threshold | 5.15 碌s(+5.52%)Baseline: 4.88 碌s | 5.83 碌s (88.23%) |
| Adapter::Magic (Rust) | 馃搱 view plot 馃毞 view threshold | 26.74 碌s(-0.79%)Baseline: 26.95 碌s | 30.12 碌s (88.77%) |
| Adapter::Rust | 馃搱 view plot 馃毞 view threshold | 4.67 碌s(+7.66%)Baseline: 4.33 碌s | 6.65 碌s (70.19%) |
| Adapter::RustBench | 馃搱 view plot 馃毞 view threshold | 4.66 碌s(+7.58%)Baseline: 4.33 碌s | 6.64 碌s (70.12%) |
epompeii
marked this pull request as ready for review
September 18, 2026 07:47
epompeii
marked this pull request as draft
October 1, 2026 02:26
epompeii
force-pushed
the
u/ep/s3-r2/server-backup
branch
from
October 1, 2026 05:43
3f36999 to
9a8fed7
Compare
epompeii
marked this pull request as ready for review
October 1, 2026 06:14
The POST /v0/server/backup endpoint, the bencher server backup CLI subcommand, and the database.data_store server config section are gone. Continuous replication under plus.disaster_recovery is the supported path, so bencher_schema no longer depends on the AWS SDK. A config that still carries database.data_store is ignored.
epompeii
marked this pull request as draft
October 3, 2026 19:02
epompeii
force-pushed
the
u/ep/s3-r2/server-backup
branch
from
October 3, 2026 19:34
9a8fed7 to
ec13c3d
Compare
epompeii
marked this pull request as ready for review
October 4, 2026 16:44
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The on demand database backup predates continuous replication and is unused. Its config section,
database.data_store, took an AWS S3 access point ARN and was the only reasonbencher_schemadepended on the AWS SDK. Continuous replication underplus.disaster_recoveryis the supported path.Changes
POST /v0/server/backupand its OPTIONS handler are removed, and the OpenAPI spec is regenerated.bencher server backupis removed from the CLI.database.data_storeand its types are removed from the server config;bencher_schemadropsaws-sdk-s3andaws-credential-types, and the root manifest dropsasync-compressionandrusqlite, which had no user left.caminobecomes aplusdependency ofbencher_schema, its only remaining user being plus-gated, and tokio'sfsfeature goes with the lasttokio::fscall.data_store; the disaster recovery pages no longer refer to backups, and the self-hosted skill links disaster recovery to its explanation page.databasesection still carryingdata_storedeserializes with its other fields intact, so a stale config never fails to boot.Breaking changes
POST /v0/server/backupandbencher server backupare gone.database.data_storeis ignored. Remove the section.Second of a stack of three, on top of the
plus.disaster_recoveryrename. The last PR moves the container registry storage ontoobject_store, at which point the AWS SDK leaves the workspace.