GPUI paints a frame by recording primitives (quads, shadows, paths, underlines, glyph sprites, surfaces) into a `Scene`. The renderer then draws the scene's primitives back to front, so that later primitives paint over earlier ones. This means every pixel of every primitive is shaded, even where a later primitive completely covers it. In heavily nested UI, this adds up to a lot of overdraw. Inspired by WebRender, we reduce overdraw with a depth buffer and two passes: - The opaque pass draws quads that we know cover their whole area with an opaque color. They're drawn front to back, with depth testing and depth writes enabled. In practice, we can only make this guarantee for quads with a solid, fully opaque fill and no rounded corners. - The blended pass draws everything else back to front, with depth testing enabled but depth writes disabled. This is essentially the existing render loop with a depth test added. Any fragment 'behind' an opaque quad fails the depth test and is never shaded. To get more of each frame into the opaque pass, `paint_quad` now splits any quad with rounded corners into a rectangular interior and the four edge strips around it. The interior is a plain rectangle, so if its fill is solid and opaque, it's drawn in the opaque pass, and only the strips need the border and corner shading. Measured on an Intel HD 4600: Scene | Before | After | Change | Pixel shader invocations | |---|---|---|---|---| | Editor | 3,941µs | 1,689µs | −57% | 3.71M → 1.65M (−55%) | | Command palette | 7,658µs | 2,275µs | −70% | 5.33M → 1.80M (−66%) | | Git Graph | 3,589µs | 1,889µs | −47% | 3.13M → 1.65M (−47%) | Fixes https://github.com/zed-industries/zed/issues/8043 Release Notes: - Reduced GPU usage - [GPUI] Improved rendering performance by skipping pixels hidden behind opaque quads
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.