#146

feat: add support for Nix via a flake

s12d ago

← Back to list

01Issue

BugShippedSwamp CLITeam

Assigneesstack72

Relationships

#918 model evaluate is slow resolving data.latest expressions in large datastores

Opened by evrardjp · 7/2/2026· Shipped 7/2/2026

Summary

swamp model evaluate can spend ~30-35s at expression evaluation for a single model that contains only a few data.latest(...) expressions, even when reading the referenced data directly takes ~1s.

This appears to be a performance bug in model expression evaluation: resolving a targeted data.latest(modelName, dataName) expression seems to pay a broad datastore/catalog scan cost, possibly repeated per expression, rather than using the direct data lookup path.

Reproduction

A model has global arguments like:

globalArguments:
  host: ${{ data.latest("lab-vm-pool", "vaultwarden").attributes.ipAddress }}
  user: ${{ data.latest("lab-vm-pool", "vaultwarden").attributes.bootstrapSSHUser.username }}
  hostKeyPath: ${{ data.latest("lab-vm-pool", "vaultwarden").attributes.sshHostCertificate.hostKeyPath }}

Timing the evaluation:

time swamp model evaluate vaultwarden-host-key --json

Observed: about 30-35 seconds, with high memory usage observed around 2GB RSS in one run.

But the directly referenced data is fast to retrieve:

time swamp data get lab-vm-pool vaultwarden --json >/tmp/vw.json

Observed: about 1 second.

The repository has a large .swamp/data tree, including multi-GB data for unrelated models. The referenced lab-vm-pool/vaultwarden data itself is small.

Expected behavior

data.latest("lab-vm-pool", "vaultwarden") during model evaluation should use an indexed/direct lookup comparable to swamp data get lab-vm-pool vaultwarden, and should not scan or load unrelated data. Multiple references to the same data item in one model evaluation should also ideally be cached within the evaluation.

Actual behavior

swamp model evaluate takes ~30-35s at expression evaluation, while the target data lookup takes ~1s.

Environment

Current swamp version:

20260630.112427.0-sha.0e5078e9

swamp update --check --json reports a newer version is available (20260702.171037.0-sha.ca29630a), but source-version comparison was inconclusive because swamp source fetch --version 20260702.171037.0-sha.ca29630a failed in this environment with Read-only file system (os error 30): mkdir '/var/home/<USERNAME>/.swamp/source'.

02Bog Flow

Shipped

7/2/2026, 8:32:12 PM

Click a lifecycle step above to view its details.

03Sludge Pulse

stack72 assigned stack727/2/2026, 5:50:00 PM

stack72 commented 7/2/2026, 8:32:22 PM

Thanks @evrardjp for reporting this! The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

Scorecard: beta/rc-only extensions show "not scored" despite successful scoring (GET /score resolves only latestVersion)

`swamp extension search --channel beta|rc|stable` ignores the filter — all channels + the no-flag default return an identical result set

Beta-channel extensions are never scored — perpetual 'Scoring is taking longer than expected'

feat: allow models to call other models mid-execution via context.runModel()

swamp-club: enable OAuth provider for swamp serve collective-based admission

extension update/install reports new version while on-disk pulled files stay old

command/shell: step with timeout + a surviving child process reports exit -1 despite command exiting 0

swamp serve startup/shutdown is very slow on large repo and lacks diagnostics

Vault push log overstates what left the machine: Pushed N vault file(s) to datastore counts every dirty file, not just vault files

serve-auth: mode: oauth — device grant client + collective-based admission

serve-auth: enable OIDC Provider + Device Authorization plugins in swamp-club

Orphaned data (migrated-away/deleted model) can't be GC'd or deleted

Docs: document swamp data prune (orphaned-data reclamation)

UAT: CLI coverage for swamp data prune (orphaned-data reclamation)

Session credential revocation scans entire credential map on every dispatch completion

Docs: update worker-commands.md for --all flag and JSON output change

datastore migrate-index aborts on hardcoded 30s S3 requestTimeout for large shards

swamp worker list: hide disconnected workers by default, add --all flag

swamp serve should survive bad extension failures

Worker fleets phase 7: how-to guides and explanation docs

swamp serve: catch unhandled promise rejections from extensions

[@adam/cfgmgmt] SSH helper can crash swamp serve via unhandled finally() rejection

Docs: add --server-token flag to worker connect reference

Add --server-token to worker connect for authenticated orchestrators

Docs: document --trusted-hosts flag for swamp serve

Document SWAMP_SERVE_EXTRA_HEADERS for reverse proxy/tunnel setups

Add --trusted-hosts flag to swamp serve for Docker/Kubernetes worker connections

Allow swamp clients to send custom headers when connecting to swamp serve

Docs: update serve-flags.md default queue timeout from 60s to 10m

Worker fleets phase 6: raise default queue timeout to 10 minutes

Worker fleets phase 4b: capacity slots and concurrent dispatch

MethodContext docs/comments mention context.putSecret but runtime exposes vaultService.put

Docs: add --concurrency flag and SLOTS column to worker-commands reference

install.sh still points users to systeminit/swamp

Support user systemd units for 'swamp serve daemon enable'

swamp serve scheduled execution runs steps in an isolated data scope: readResource sees empty state, writeResource never reaches the model-scope chain — stateful scheduled workflows duplicate instead of deduplicating

Support installing swamp via mise GitHub backend

Worker fleets phase 4a: dispatch runner extraction — child process per dispatch

Docs: add swamp worker daemon enable/disable/status to worker-commands reference

Worker fleets phase 3 PR2: swamp worker daemon enable

Docs: add drain, lifecycle policies, and exit-code contract to references

Worker fleets phase 3 PR1: drain state machine, lifecycle policies, signal handling

Leaderboard search excludes ghosts — a visible ghost can't be found by its alias

issue-lifecycle: plan lifecycle entry silently dropped when summary exceeds 1000 chars

Docs: add worker verify, --verify-on-enroll, and env-var config to references

Labs - Filters do not apply to Blocked status and Billing Tier category

Worker fleets phase 2 PR2: env-var config, swamp worker verify, --verify-on-enroll

Docs: add --type flag to issue edit reference and how-to

Docs: update manual with whole-field expression syntax for workflow task inputs/globalArgs

Allow changing an existing issue to security/confidential after submission

Allow dynamic object expressions for workflow task inputs/globalArgs

Docs: update enrollment token references for fleet tokens (--max-enrollments)

Worker fleets phase 2 PR1: fleet tokens (--max-enrollments, bindings, worker naming)

$identify events are never consumed — anonymous web history never binds to the account

Worker fleets phase 1 PR3: boot reconciliation and integration test

Login success still shows login tip

Support confidential visibility for non-security issues

Fine-grained scopes for swamp.club access tokens

Add associative info to user profiles: collective membership + collaborative contributions

Remove comments from /feed and redesign the page

feed_post_score_events queue grows unboundedly (no TTL, no delete-on-delivery)

Make paid subscribers visually stand out (badge, profile popup summary)

Relax the profanity filter

Giphy integration via /giphy command

@-mention autocomplete for users when writing lab ripples

Worker fleets phase 1 PR2: step_queued events, pending-dispatch model, queue introspection

Docs: add swamp worker queue to worker-commands reference

/lab shipped list is sorted by issue number, not ship date

Docs: update manual for ephemeral data and step-output dependency deferral

Docs: update remote execution references for elastic queueing

Support dynamic host discovery from external sources

Worker fleets phase 1: elastic queueing

catalog backfill should support scoped population for targeted lookups

Docs: document global skill sync behavior for custom tools in manual

swamp update syncs global skills to default agent directories instead of configured custom Pi skillsDir

coerceToSuffix does not sanitize path-unsafe characters, causing forEach items and vary dimensions with / to produce invalid data instance names

Badge for activity on other people's issues

swamp serve: add @keychain=<service>/<account> indirection for secret args on macOS

swamp serve: eliminate wrapper scripts via @vault= secret refs and native startup hooks

Automate mechanical frontmatter fixes in the fixing stage