4 ms·

I cannot stress how much I do not want my 300w gpu to be used to render text that change at most three times per second. And it's not just about electricity co

I cannot stress how much I do not want my 300w gpu to be used to render text that change at most three times per second. And it's not just about electricity cost and heat stress, it will conflict with everything else that requires the gpu to do stuff, including watching 4k videos on the second monitor, which does have a legitimate case for requiring hardware acceleration since they move a lot of data 60 times per second, and your editor doesn't. And the limited resource is not the gpu itself but the nearby onboard memory is a scarce resource on its own. I'd be real mad at a software that prevents me to multitask.

alexfromapex 4y ago
This UI is so lightweight it seems like they should easily be able to toggle the GPU compute on or off
ohgodplsno 4y ago
I have horrible news to tell you about compositors: they already do use your GPU, even if you're watching a 4K video on the side. Even when requesting a full screen swapchain to avoid having to deal with the compositor, modern OSes will force you to go through that compositor and lie about it being fullscreen. Additionally, using your GPU doesn't mean locking your GPU on that task. Your 4K video most likely isn't taking up 100% of GPU time, nor 100% of the nearby onboard memory. Everyone already gets a share of that time.
- avereveard 4y ago
  Compositor and ui framework that interact with them know that 120fps is not the target but that frame render time is, and know not to have active rendering contexts for static resources. Chasing 120fps rendering here is the problem.
- rafram 4y ago
  > Even when requesting a full screen swapchain to avoid having to deal with the compositor, modern OSes will force you to go through that compositor and lie about it being fullscreen. I’m honestly thankful for this bit of lying. Windows 8 and below had horrible, horrible issues with fullscreen programs, especially games - they’d change your screen resolution and thus move and resize all your other windows, they’d freeze for ten seconds when you tried to alt-tab out, and they’d frequently just crash when you switched back to them. Those problems are essentially nonexistent nowadays, and it’s worth the small performance cost that comes from going through the compositor.
  - ohgodplsno 4y ago
    I know that in Windows 10+ and on UWP apps, requesting a fullscreen swapchain straight up crashes and tells you "nope, you're going to go through the compositor". But yes, alt-tabbing Source games was an exercise in patience.
    - rafram 4y ago
      Is that disabled for programs targeting older OS versions? Or are you saying that the new behavior is only for UWP apps? Because that sounds like it would break a lot of old code.
      - ohgodplsno 4y ago
        Sorry, hadn't seen that response: yes, it's only when you opt in to UWP that it causes crashes. However, even if you didn't, Windows lies to you. If you ask for FSE (Full Screen Exclusive), it'll say alright buddy, and give you a Full screen that goes through DWM. I believe they have an article on that somewhere on the direct X blog called full screen optimizations, or something along those lines, that explains it.
TiredOfLife 4y ago
Unless you use Templeos your OS is already using gpu to do gui rendering and composing.
- avereveard 4y ago
  For one that's not entirely true. standard windows gui calls are backed by a shared surface and accumulate drawing instruction on the system side of the render surface,managed by the cpu render pipeline, so that they can keep a dirty rectangle list and only update the dirty areas of the gpu side of the shared surface. From there composing runs on the gpu. Then again the issue is the focus of rendering at 120fps.the rendering context should be paused between the vast nothingness that happens in between user keystrokes, that happen at something like 4kp, and in burst. The insistence on 120fps is the issue here, not the rendering pipeline.
  - ben-schaaf 4y ago
    That's already what they're doing: https://news.ycombinator.com/item?id=35080427 https://news.ycombinator.com/item?id=35080427
    - avereveard 4y ago
      That's even weirder why would they redraw the whole application on a character change
      - rstat1 4y ago
        Where did they say they were doing that? All I see is them saying they can, not that they are.
KptMarchewa 4y ago
Processors could throttle themselves since the 90s. GPUs can too.

alexfromapex 4y ago

This UI is so lightweight it seems like they should easily be able to toggle the GPU compute on or off

ohgodplsno 4y ago

I have horrible news to tell you about compositors: they already do use your GPU, even if you're watching a 4K video on the side. Even when requesting a full screen swapchain to avoid having to deal with the compositor, modern OSes will force you to go through that compositor and lie about it being fullscreen. Additionally, using your GPU doesn't mean locking your GPU on that task. Your 4K video most likely isn't taking up 100% of GPU time, nor 100% of the nearby onboard memory. Everyone already gets a share of that time.

avereveard 4y ago
Compositor and ui framework that interact with them know that 120fps is not the target but that frame render time is, and know not to have active rendering contexts for static resources. Chasing 120fps rendering here is the problem.
rafram 4y ago
> Even when requesting a full screen swapchain to avoid having to deal with the compositor, modern OSes will force you to go through that compositor and lie about it being fullscreen. I’m honestly thankful for this bit of lying. Windows 8 and below had horrible, horrible issues with fullscreen programs, especially games - they’d change your screen resolution and thus move and resize all your other windows, they’d freeze for ten seconds when you tried to alt-tab out, and they’d frequently just crash when you switched back to them. Those problems are essentially nonexistent nowadays, and it’s worth the small performance cost that comes from going through the compositor.
- ohgodplsno 4y ago
  I know that in Windows 10+ and on UWP apps, requesting a fullscreen swapchain straight up crashes and tells you "nope, you're going to go through the compositor". But yes, alt-tabbing Source games was an exercise in patience.
  - rafram 4y ago
    Is that disabled for programs targeting older OS versions? Or are you saying that the new behavior is only for UWP apps? Because that sounds like it would break a lot of old code.
    - ohgodplsno 4y ago
      Sorry, hadn't seen that response: yes, it's only when you opt in to UWP that it causes crashes. However, even if you didn't, Windows lies to you. If you ask for FSE (Full Screen Exclusive), it'll say alright buddy, and give you a Full screen that goes through DWM. I believe they have an article on that somewhere on the direct X blog called full screen optimizations, or something along those lines, that explains it.

TiredOfLife 4y ago

Unless you use Templeos your OS is already using gpu to do gui rendering and composing.

avereveard 4y ago
For one that's not entirely true. standard windows gui calls are backed by a shared surface and accumulate drawing instruction on the system side of the render surface,managed by the cpu render pipeline, so that they can keep a dirty rectangle list and only update the dirty areas of the gpu side of the shared surface. From there composing runs on the gpu. Then again the issue is the focus of rendering at 120fps.the rendering context should be paused between the vast nothingness that happens in between user keystrokes, that happen at something like 4kp, and in burst. The insistence on 120fps is the issue here, not the rendering pipeline.
- ben-schaaf 4y ago
  That's already what they're doing: https://news.ycombinator.com/item?id=35080427 https://news.ycombinator.com/item?id=35080427
  - avereveard 4y ago
    That's even weirder why would they redraw the whole application on a character change
    - rstat1 4y ago
      Where did they say they were doing that? All I see is them saying they can, not that they are.

KptMarchewa 4y ago

Processors could throttle themselves since the 90s. GPUs can too.