Part of #64897. Also fixes the `threads.db` read traffic and lock stalls reported in [this comment on #59107](https://github.com/zed-industries/zed/issues/59107#issuecomment-5781374977). During long agent sessions, Zed kept reading the whole `threads.db` file in the background. The reporter saw about 150 MB/s of reads. After every save, we reload the thread list. That only needs small fields like the title and dates. But some of those fields were added to the table later, so SQLite stores them after each thread's large `data` blob, and has to go through the whole blob to reach them. On a 148 MB test database with 120 threads, one reload read 37,958 pages, which is the entire file. This adds an index that holds just the fields the thread list needs. SQLite now reads the list from the index and skips the blobs, and the same reload reads 7 pages. The index starts with the dates, so SQLite also gets the threads in newest-first order without sorting, but that part is minor. A test checks that SQLite actually uses the index. Moving `data` to the end of the table would fix it too. But `threads.db` has no migration tracking, and that change would copy every thread's blob on first launch. I went with the index since it's safer and doesn't touch any existing rows. Saving a thread 200 times in a row on that database (release build): | | Before | After | |---|---|---| | Time per save | 22.2 ms | 2.4 ms | | CPU time for 200 saves | 4.4 s | 0.47 s | Memory use stays the same. The index takes about 24 KB, and Zed builds it once on first launch, in the background. That took about 0.1 s for 148 MB. Next, I'd like to update only the saved thread in the list, so we don't reload the whole list after every save. That'll be a follow-up PR. Release Notes: - Improved CPU usage and disk reads while the agent is working, especially with a long thread history. --------- Co-authored-by: zed-zippy[bot] <234243425+zed-zippy[bot]@users.noreply.github.com>
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking discussion)
Developing Zed
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
Zed source code is licensed primarily under GPL-3.0-or-later, with Apache-2.0 components where marked.
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.
Sponsorship
Zed is developed by Zed Industries, Inc., a for-profit company.
If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.