3 ms·

I had a relatively recent graphics card (5 years old perhaps?). I don't care about 3D or games, or whatever. So I was sad not to be able to run a text editor (

I had a relatively recent graphics card (5 years old perhaps?). I don't care about 3D or games, or whatever. So I was sad not to be able to run a text editor (let's be honest, Zed is nice but it's just displaying text). And somehow the non-accelerated version is eating 24 cores. Just for text. https://github.com/zed-industries/zed/discussions/23623 https://github.com/zed-industries/zed/discussions/23623 I ended up buying a new graphics card in the end. I just wish everyone could get along somehow.

ronsor 8mo ago
The fact that we need advanced GPU acceleration for a text editor is concerning.
- ianlevesque 8mo ago
  Text editor developers get bored too!
- deleted 8mo ago
  [deleted]
- jsheard 8mo ago
  Such is life when built-in laptop displays are now pushing a billion pixels per second, rendering anything on the CPU adds up fast. Sublime Text spent over a decade tuning their CPU renderer and it still didn't cut it at high resolutions. https://www.sublimetext.com/blog/articles/hardware-accelerated-rendering https://www.sublimetext.com/blog/articles/hardware-accelerat...
  - the8472 8mo ago
    Most of the pixels don't change every second though. Compositors do have damage tracking APIs, so you only need to render that which changed. Scrolling can be mostly offset transforms (browsers do that, they'd be unbearably slow otherwise).
    - simonask 8mo ago
      That’s not the slow part. The slow part is moving any data at all to the GPU - doesn’t super matter if it’s a megabyte or a kilobyte. And you need it there anyway, because that’s what the display is attached to. Now, the situation is that your display is directly attached to a humongously overpowered beefcake of a coprocessor (the GPU), which is hyper-optimized for calculating pixel stuff, and it can do it orders of magnitude faster than you can tell it manually how to update even a single pixel. Not using it is silly when you look at it that way.
      - Dylan16807 8mo ago
        Sure, use it. But it very much shouldn't be needed, and if there's a bug keeping you from using it your performance outside video games should still be fine. Your average new frame only changes a couple pixels, and a CPU can copy rectangles at full memory speed.
      - imtringued 8mo ago
        I'm kinda weirded out by the fact that their renderer takes 3ms on a desktop graphics card that is capable of rendering way more demanding 3D scenes in a video game.
      - afandian 8mo ago
        I have no problem with it squeezing out the last few percent using the GPU. But look at my CPU charts in the github link upthread. I understand that maybe that's due to the CPU emulating a GPU? But from a thousand feet, that's not viable for a text editor.
        jsheard 8mo ago
        Yeah LLVMpipe means it's emulating the GPU path on the CPU, which is really not what you want. What GPU do you have out of interest? You have to go back pretty far to find something which doesn't support Vulkan at all, it's possible that you do have Vulkan but not the feature set Zed currently expects.

ronsor 8mo ago

The fact that we need advanced GPU acceleration for a text editor is concerning.

ianlevesque 8mo ago
Text editor developers get bored too!
deleted 8mo ago
[deleted]
jsheard 8mo ago
Such is life when built-in laptop displays are now pushing a billion pixels per second, rendering anything on the CPU adds up fast. Sublime Text spent over a decade tuning their CPU renderer and it still didn't cut it at high resolutions. https://www.sublimetext.com/blog/articles/hardware-accelerated-rendering https://www.sublimetext.com/blog/articles/hardware-accelerat...
- the8472 8mo ago
  Most of the pixels don't change every second though. Compositors do have damage tracking APIs, so you only need to render that which changed. Scrolling can be mostly offset transforms (browsers do that, they'd be unbearably slow otherwise).
  - simonask 8mo ago
    That’s not the slow part. The slow part is moving any data at all to the GPU - doesn’t super matter if it’s a megabyte or a kilobyte. And you need it there anyway, because that’s what the display is attached to. Now, the situation is that your display is directly attached to a humongously overpowered beefcake of a coprocessor (the GPU), which is hyper-optimized for calculating pixel stuff, and it can do it orders of magnitude faster than you can tell it manually how to update even a single pixel. Not using it is silly when you look at it that way.
    - Dylan16807 8mo ago
      Sure, use it. But it very much shouldn't be needed, and if there's a bug keeping you from using it your performance outside video games should still be fine. Your average new frame only changes a couple pixels, and a CPU can copy rectangles at full memory speed.
    - imtringued 8mo ago
      I'm kinda weirded out by the fact that their renderer takes 3ms on a desktop graphics card that is capable of rendering way more demanding 3D scenes in a video game.
    - afandian 8mo ago
      I have no problem with it squeezing out the last few percent using the GPU. But look at my CPU charts in the github link upthread. I understand that maybe that's due to the CPU emulating a GPU? But from a thousand feet, that's not viable for a text editor.
      - jsheard 8mo ago
        Yeah LLVMpipe means it's emulating the GPU path on the CPU, which is really not what you want. What GPU do you have out of interest? You have to go back pretty far to find something which doesn't support Vulkan at all, it's possible that you do have Vulkan but not the feature set Zed currently expects.