# ci: Use a smaller Linux runner for migration checks \(\#64240\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/bf9a360110cb002b1e0bf6a7b1764849f65a3d95)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: bf9a360110cb002b1e0bf6a7b1764849f65a3d95

Requested commit: bf9a360110cb002b1e0bf6a7b1764849f65a3d95

Commit: bf9a360110cb002b1e0bf6a7b1764849f65a3d95

Tree: ed3381b523c36be9e7042addb198579128e326dc

Author: Piotr Osiewicz

Committer: GitHub

## Message

```
ci: Use a smaller Linux runner for migration checks (#64240)

## Summary

Move `check_postgres_and_protobuf_migrations` from the existing 16-vCPU
/ 32-GiB Linux runner to the existing 8-vCPU / 16-GiB runner. The job
handles Git history and Buf compatibility, lint, and formatting checks;
its commands, triggers, and coverage remain unchanged.

This reduces its concurrent CPU and memory allocation by half. Namespace
observations from September 11–14 covered 224 runs, with a typical job
duration of 37 seconds and maximum observed RAM around 1.5 GiB. The p95
of per-run peak CPU usage was about 7.7 cores, so CI runtime on the
smaller profile should be checked rather than assuming identical
performance.

Updated the Rust workflow generator and regenerated the YAML. No other
jobs are changed.

## Validation

- `cargo xtask workflows`
- `cargo fmt -p xtask -- --check`
- `git diff --check`
- Full diff reviewed: two files, only the runner selection changed.
- Actual migration check on the smaller runner awaits CI.

Release Notes:

- N/A
```

## Parents

- [93f9fce1152dc6b9e345847753e667e3db6dba5c](https://git.cafe/gitcafe/zed/commit/93f9fce1152dc6b9e345847753e667e3db6dba5c?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/bf9a360110cb002b1e0bf6a7b1764849f65a3d95?format=markdown)