learn-wgpu
flamegraph
Our great sponsors
learn-wgpu | flamegraph | |
---|---|---|
75 | 47 | |
1,382 | 4,241 | |
- | 2.4% | |
8.0 | 7.4 | |
18 days ago | 8 days ago | |
Rust | Rust | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
learn-wgpu
-
Practicing Rust, Learning Bevy, Creating a WASM Snake Game for the Browser
Nice.
Speaking of Snake game, if you want to go even deeper, you can try to use the wgpu crate to combine Rust and WebGPU to write everything from scratch. Here is the tutorial:
https://sotrh.github.io/learn-wgpu/#what-is-wgpu
I once wrote a code editor with wgpu, from font rendering to char/line state management (very rough) for music live coding:
https://github.com/glicol/glicol-wgpu
It runs in browsers, even including Safari!
- Please review my ECS geospatial engine so far
- Help me get started with 3D graphics in Rust
-
Realtime Ray Marching implemented with Rust and wgpu
https://sotrh.github.io/learn-wgpu/ This is probably the best resource out there for learning wgpu specifically. If you're unfamiliar with graphics, the learnopengl one is good. If you've got experience though, jumping right into that one is a shout or looking at some vulkan ones as they're pretty similar in terms of architecture.
-
Is it possible and realistic to learn independent of an API?
- https://sotrh.github.io/learn-wgpu
-
What would be a good project structure/ design for a game engine using WebGPU?
Most of The WGPU I learnt is from https://sotrh.github.io/learn-wgpu/ but it doesn't really talk about designing n stuff, I thought of checking out the source code for Bevy or even games like veloren. But well, their codebases are pretty big to get started in the first place.
- Learn Wgpu
-
Learning OpenGL before wgpu?
So I was wondering if opting for option 1 would be better to begin with. OpenGL has a much bigger community and wgpu only has its documentation which I hear is not quite up there yet. There is this excellent tutorial for wgpu that I read through, but it seems like wgpu can be a lot more complicated than starting with OpenGL.
-
Getting started with computer graphics with Rust
I started with wgpu tutorial (https://sotrh.github.io/learn-wgpu/) since I like the idea of portability and it's a Rust-first library, but it seems I'm missing some foundations of how CG works in general: the code is given, a little of explanation like it assumes I already know something, maybe I'm wrong, but I wish there was a longer explicit version.
-
Trying to learn wgpu
If you haven't seen it: https://sotrh.github.io/learn-wgpu/ is a good introduction that will explain most of what you asked, then can refer to rend3d or bevys renderer to see how a render graph works.
flamegraph
-
Rust Tooling: 8 tools that will increase your productivity
You can install cargo-flamegraph with cargo install flamegraph. There are some underlying requirements to be able to use cargo-flamegraph; you will want to take a look at the repo here to make sure you have the right dependencies.
-
Need help making sense of these benchmark results
I tried to diagnose the issue with flamegraph, but unfortunately the flamegraph didn't show anything beyond the next call for some reason
-
Why is my code so slow ? advent of code 2022, day 16 (basic graph stuff)
having some tools to identify slowness origins (flamegraph is one... but not sure it's the way to go)
-
why is my code so slow ? advent of code 2023, day 16 (basic graph stuff)
I'm currently implementing a solution for the first part of the day 16. It work but it is really slow... I'd like to : - understand why - having some tools to identify slowness origins (flamegraph is one... but not sure it's the way to go) - eventually have some clue/solution/idea - have general feedback on what in my "coding style" is not appropriate for rust (I come from java/kotlin/ts even if I've already coded a bit in c/c++) : for example I love iterator & sequence but i feel they are not really suited to overuse in rust (mostly because of async & result).
-
how expensive is an operation?
Use a profiler. Flamegraph is a good way to visualise profiler output. This lets you identify which functions are taking up a large amount of time - and hence helps you identify where to focus your optimisation efforts.
-
Slow Rust Redis
You tried trying to see what takes the most time under load via flames? https://github.com/flamegraph-rs/flamegraph
- making a virtual machine in rust
-
Need help with rust performance
Well, in cases like that the answer is straight forward, use a profiler like https://github.com/flamegraph-rs/flamegraph
-
superdiff - a way to find similar code blocks in projects (comments appreciated)
I don't see any obvious problems with your algorithm. I've had luck using cargo-flamegraph to identify the slow parts of my code. That's going to show you which parts to focus on improving the performance of!
-
Data-driven performance optimization with Rust and Miri
From the readme of cargo flamegraph:
What are some alternatives?
ash - Vulkan bindings for Rust
cargo-flamegraph - Easy flamegraphs for Rust projects and everything else, without Perl or pipes <3
glium - Safe OpenGL wrapper for the Rust language.
tracing - Application level tracing for Rust.
SDL - Simple Directmedia Layer
tensorflow_macos - TensorFlow for macOS 11.0+ accelerated using Apple's ML Compute framework.
winit - Window handling library in pure Rust
hashbrown - Rust port of Google's SwissTable hash map
egui - egui: an easy-to-use immediate mode GUI in Rust that runs on both web and native
heaptrack - A heap memory profiler for Linux
wgsl-mode - Emacs syntax highlighting for the WebGPU Shading Language (WGSL)
snmalloc-rs - rust bindings of snmalloc