[jgoux]

Summary

Local stack services can now be given container resource limits in config.toml:

[local.services.database.container]
memory = "2GiB"
cpus = 1.5

• memory is a 1024-based size (512MiB, 1GiB; a bare number is bytes). Swap is capped at the same amount, so the limit is not silently doubled.
• cpus is a positive number of CPUs; fractions are allowed.
• Limits apply to every container launch, so they survive stack stop and stack start. Editing them shows as configuration drift in stack status until the stack is stopped and started again.
• The table describes containers only: the native runtime ignores it, so one config.toml keeps working with both runtimes.
• The out-of-memory hint now points to the new memory setting.

[github-actions]

CLI benchmark (Lightweight Commands): no changes found

Commit e0a2115 against develop at d8f66a0 · 10 runs each · report only, never blocks merging

Command	Workload	Before	After	Change
supabase --version	version	222 ms	228 ms	no real change
supabase --help	help	213 ms	212 ms	no real change
supabase init	init	223 ms	221 ms	no real change
supabase migration new bench	migration-new	210 ms	217 ms	no real change
supabase config convert	config-convert	219 ms	230 ms	no real change (+5%, within normal variation)
supabase gen types --lang typescript --project-id replayfixtureprojref	gen-types	247 ms	265 ms	no real change (+7%, within normal variation)
supabase projects list	projects-list	237 ms	237 ms	no real change
supabase functions list --project-ref replayfixtureprojref	functions-list	272 ms	248 ms	no real change (-9%, within normal variation)

API calls: unchanged for all 8 commands.

Binary size: 134.8 MB, up 8.0 KB from 134.8 MB.

Details: timing ranges, API calls per command, slowest phases

Timing ranges

Command	Workload	Before range	After range	Change	Verdict
supabase --version	version	205-243 ms	212-252 ms	+7 ms (+3%)	within noise
supabase --help	help	198-250 ms	199-246 ms	-1 ms (-1%)	within noise
supabase init	init	214-235 ms	197-239 ms	-1 ms (-1%)	within noise
supabase migration new bench	migration-new	203-232 ms	199-240 ms	+7 ms (+3%)	within noise
supabase config convert	config-convert	198-240 ms	209-250 ms	+11 ms (+5%)	within noise
supabase gen types --lang typescript --project-id replayfixtureprojref	gen-types	237-285 ms	232-290 ms	+18 ms (+7%)	within noise
supabase projects list	projects-list	200-267 ms	216-274 ms	+0 ms (+0%)	within noise
supabase functions list --project-ref replayfixtureprojref	functions-list	219-332 ms	233-276 ms	-24 ms (-9%)	within noise

API calls per command

Command	Workload	Before	After	Endpoint changes
supabase --version	version	0	0
supabase --help	help	0	0
supabase init	init	0	0
supabase migration new bench	migration-new	0	0
supabase config convert	config-convert	0	0
supabase gen types --lang typescript --project-id replayfixtureprojref	gen-types	2	2
supabase projects list	projects-list	1	1
supabase functions list --project-ref replayfixtureprojref	functions-list	2	2

Slowest phases

No command moved beyond noise, so there are no phase deltas.

Workflow run

Comment /bench to run the lightweight benchmark (this comment) again on the latest commit, or /bench full to also run the integration-heavy benchmark, which posts in its own comment.