Tilt becomes sluggish after log size grows very large
Open
@jazzdan is already working on this.
Since Jun 1, 2020.
bug
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Our developers will occasionally leave Tilt running for a long time and/or launch services in DEBUG mode and a lot of content will be logged. After a while, so much content is logged that Tilt becomes sluggish and other issues like https://github.com/tilt-dev/tilt/issues/3194 appear.
It would be nice if k8s_resource was extended to allow developers to set a maximum number of log lines for Tilt to retain on a per-service basis (and/or if there was a global flag to set a default to be applied across all services).
This would potentially also resolve some of the drivers behind https://github.com/tilt-dev/tilt/issues/1885
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.