4 ms·

I understand that this is a demo, but actually drawing all 8,000 nodes instead of just 3 screenfuls (6 nodes on my screen) and updating them dynamically when sc

I understand that this is a demo, but actually drawing all 8,000 nodes instead of just 3 screenfuls (6 nodes on my screen) and updating them dynamically when scrolling isn't what I would call 'performant', but needless waste of resources. Btw: when clicking any 'task' to get to see the details, I see a repeating pattern of almost vertical stripes in some colors. I guess that's not what it should look like.

birracerveza 4y ago
If drawing all 8000 nodes consumes less resources than rendering your average homepage, is it really wasteful? I understand it can be optimized, but that optimization often comes at a cost which may end up being even more wasteful.
- galangalalgol 4y ago
  Yeah, when a gpu is involved it is often cheaper to process everything rather than check what meeds to be processed.
  - ReleaseCandidat 4y ago
    I don't know how egui or the OP's app works, but we aren't talking about costly intersections of arbitrary surfaces but the sending of vertex data (for the vertex shader) in an integer interval (of nodes). This isn't about half or 1/10, but about 1/1000th of the data.
- ReleaseCandidat 4y ago
  > If drawing all 8000 nodes consumes less resources than rendering your average homepage, is it really wasteful? That may not have been clear, but I am talking about drawing less nodes in any case, also when using egui.
flohofwoe 4y ago
In Spector.js it looks like the demo is using a very small number of draw calls, and those can sometimes have hundreds of thousands of triangles. For old low-end mobile GPUs this might start to become a problem, but it's nothing for the last 20 years of desktop GPUs. In any case, it looks like a good base for further optimisation to ignore offscreen UI elements early (e.g. not sure if egui has something like Dear ImGui's ListClipper).

4 ms·

I understand that this is a demo, but actually drawing all 8,000 nodes instead of just 3 screenfuls (6 nodes on my screen) and updating them dynamically when sc

by ReleaseCandidat 4y ago

birracerveza 4y ago
If drawing all 8000 nodes consumes less resources than rendering your average homepage, is it really wasteful? I understand it can be optimized, but that optimization often comes at a cost which may end up being even more wasteful.
- galangalalgol 4y ago
  Yeah, when a gpu is involved it is often cheaper to process everything rather than check what meeds to be processed.
  - ReleaseCandidat 4y ago
    I don't know how egui or the OP's app works, but we aren't talking about costly intersections of arbitrary surfaces but the sending of vertex data (for the vertex shader) in an integer interval (of nodes). This isn't about half or 1/10, but about 1/1000th of the data.
- ReleaseCandidat 4y ago
  > If drawing all 8000 nodes consumes less resources than rendering your average homepage, is it really wasteful? That may not have been clear, but I am talking about drawing less nodes in any case, also when using egui.
flohofwoe 4y ago
In Spector.js it looks like the demo is using a very small number of draw calls, and those can sometimes have hundreds of thousands of triangles. For old low-end mobile GPUs this might start to become a problem, but it's nothing for the last 20 years of desktop GPUs. In any case, it looks like a good base for further optimisation to ignore offscreen UI elements early (e.g. not sure if egui has something like Dear ImGui's ListClipper).