Skip to content

docs: fix stale embedding probe batch sizes and CLI profile activation - #199

Open
detail-app[bot] wants to merge 1 commit into
devfrom
detail/fix-docs/docs-fix-stale-embedding-probe-batch-sizes-and-cli-179de8
Open

docs: fix stale embedding probe batch sizes and CLI profile activation#199
detail-app[bot] wants to merge 1 commit into
devfrom
detail/fix-docs/docs-fix-stale-embedding-probe-batch-sizes-and-cli-179de8

Conversation

@detail-app

@detail-app detail-app Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Commit 3c269b8 moved the embedding preflight probe batch sizes from 1 and 4 to 1 and 8 (persisted via the new runtime-owned batch settings under application-local.properties) and changed the CLI launcher to activate spring.profiles.active="cli,$SPRING_PROFILE" so the local profile loads the 8/8.0 batch defaults. Three living docs were left describing the old behavior.

  • docs/configuration.md and docs/github-repository-ingestion.md still stated probes use batches of 1 and 4.
  • docs/pipeline-commands.md still showed java -Dspring.profiles.active=cli without the $SPRING_PROFILE segment.

A developer following docs/pipeline-commands.md to run the CLI directly would activate only the cli profile, so application-local.properties (app.embeddings.batch-max-concurrent-requests=8, app.embeddings.batch-requests-per-second=8.0) would never load, leaving ingestion at the application.properties defaults of 1 and 1.0 — an ~8x slowdown for local ingestion.

Introduced by commit 3c269b8 (@WilliamAGH, #192)


Doc Drift PRs can be configured here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant