Compiler optimizations are the coolest thing. Like if you look at the assembly generated from the optimization level 0 it's basically doing what you'd expect doing a loop which adds all the numbers, but the optimized version figures out hey we're only ever going to be returning the same result every time we do this cause the bounds are constants so it figures out the answer compile time and makes the assembly return it.
The bigger lesson to be learned is that this is true of almost every programming language- it started in the C days and continued in nearly every compiled language and also applies to most interpreted programming languages. And the reason why different profiles/build-types/build-levels/optimization settings matter is indicated by that last term in that list; a compiler can make optimizations to instructions that make them more performant in the CPU’s machine code, and sometimes even skip human-organizational clutter (e.g. inlining functions) when it knows that line-by-line debugging isn’t required. A small introductory dip into compiler design will teach you how syntax is lexxed into symbols, and that’s constructed into an abstract syntax tree, which can be reasoned upon and simplified (like a crazier version of middle-school algebra) before finally being spit out as CPU-specific machine instructions or an assembly-like intermediary language (IL) for interpreted languages. You really don’t need a CS degree and the ability to write your own compiler to understand the basics- making sure every chunk of CPU instructions are correlated with each line of original source code is a heck of a lot slower than what a compiler (which knows a lot more about how CPUs run instructions and handle memory than most programmers) can rearrange and combine and flatten your code into.
Hi! Great video, and it's great that you added subtitles! As they currently are, though, it's a bit too long and messy and looks more like a written paragraph; this might make it a bit difficult to follow along for those reading the subtitles.
@@chrisbiscardi no, no, if it was just being sick I would've only wished you to get healthy quickly, it's fading in and out, there's static, the frequencies feel clipped. I'd recommend you redo the audio once you're feeling better and reupload a remuxed version (also wishes for being healthy again soon, cheers). (Otherwise nice info, did not know it's possible to granularly control profiles per crate)
wasm is a compilation target for the rust compiler (like wasm32-unknown-unknown), so the profiles still apply. There are a bunch of additional optimizations you can make when targeting wasm to, for example, reduce the wasm binary size. More info here: rustwasm.github.io/docs/book/reference/code-size.html
I never heard of Rust or your channel before. What are you? ... Nice voice. Almost perfect. That saliva-range noises being removed would've probably made it inescapable for most people like me, who randomly got your videos recommended. Good video still, but could be improved. Only to make more people interested in the topic, of course, because those who know about it would watch you anyway, but still.
woah!! Adding this ``` [profile.dev] opt-level = 1 [profile.dev.package."*"] opt-level = 3 ``` to my cargo.toml file was an instant ~5x speed boost while running tests. Thank you much much!
@@NabekenProG87 isn't there directly an 03 flag in rust? also how do people not know such a basic feature.... idk it feels like pointing out the obvious...
You'd be surprised how many people don't understand compiler optimisations, especially people who use IDEs that hide all this information behind a debug/release dropdown menu.
@@diadetediotedio6918 I think this discussion is completely out of topic for this video, but I do think IDEs hide a bit TOO much to the point where working around one feels like black magic. Doesn't help much then that IDE skills are generally not easy to transfer between IDEs (key exception being JetBrains' products). if I need to change a compiler configuration, I want to google "how to change compiler configuration in language x", not "how to change compiler configuration in language x in IDE y", especially if the language x in question is even somewhat obscure.
I know I've asked this question on your previous video about the release flag so thank you for the follow up video!
Your question definitely made this video happen :)
Compiler optimizations are the coolest thing. Like if you look at the assembly generated from the optimization level 0 it's basically doing what you'd expect doing a loop which adds all the numbers, but the optimized version figures out hey we're only ever going to be returning the same result every time we do this cause the bounds are constants so it figures out the answer compile time and makes the assembly return it.
Interesting, I’m new to rust so I wasn’t even aware that there was multiple profiles and what they actually meant, thanks Chris !
The bigger lesson to be learned is that this is true of almost every programming language- it started in the C days and continued in nearly every compiled language and also applies to most interpreted programming languages. And the reason why different profiles/build-types/build-levels/optimization settings matter is indicated by that last term in that list; a compiler can make optimizations to instructions that make them more performant in the CPU’s machine code, and sometimes even skip human-organizational clutter (e.g. inlining functions) when it knows that line-by-line debugging isn’t required.
A small introductory dip into compiler design will teach you how syntax is lexxed into symbols, and that’s constructed into an abstract syntax tree, which can be reasoned upon and simplified (like a crazier version of middle-school algebra) before finally being spit out as CPU-specific machine instructions or an assembly-like intermediary language (IL) for interpreted languages. You really don’t need a CS degree and the ability to write your own compiler to understand the basics- making sure every chunk of CPU instructions are correlated with each line of original source code is a heck of a lot slower than what a compiler (which knows a lot more about how CPUs run instructions and handle memory than most programmers) can rearrange and combine and flatten your code into.
i didn't search for this but thanks
I've recently started learning rust and this is good to know
Hi! Great video, and it's great that you added subtitles! As they currently are, though, it's a bit too long and messy and looks more like a written paragraph; this might make it a bit difficult to follow along for those reading the subtitles.
yup, I've since fixed the subtitle generation on the channel but haven't gotten to redoing the back catalogue yet. thanks for the reminder.
I've updated the captions for this video
@@chrisbiscardi thanks! it's a lot easier to follow along now :)
Wow! While I knew about release, I watched the video to the end just "for a checkmark", but it happened to fill a knowledge gap. Thank you!
This audio is.... in need of some filtering
not much I can do about having been sick and losing my voice earlier this week.
@@chrisbiscardi no, no, if it was just being sick I would've only wished you to get healthy quickly, it's fading in and out, there's static, the frequencies feel clipped. I'd recommend you redo the audio once you're feeling better and reupload a remuxed version (also wishes for being healthy again soon, cheers). (Otherwise nice info, did not know it's possible to granularly control profiles per crate)
@@simdimdim Maibe the recording level is too high, it was loud and not pleasant on my speakers.
But it is interesting, I had this problem once :D
The algorithm recommended this video to me, and it sure was an informative one. Thank You!
Thank for your video.
How about build for WASM. Does it have release mode too?
wasm is a compilation target for the rust compiler (like wasm32-unknown-unknown), so the profiles still apply.
There are a bunch of additional optimizations you can make when targeting wasm to, for example, reduce the wasm binary size. More info here: rustwasm.github.io/docs/book/reference/code-size.html
Bevy dynamic feature has changed.
bevy = {version = "0.10.0", features = ["dynamic_linking"]}
tbh people should at least notice that something is wrong when they look at the binary filesize (it's how i learned that there is a release flag)
for many people, using Rust is their first time using a compiled language, so they don't have that context for how big a binary should be yet
@@chrisbiscardi that's true ig
Goddamit I love rust
Thanks for the informative video!!
Thank you Chris
I never heard of Rust or your channel before. What are you?
...
Nice voice. Almost perfect. That saliva-range noises being removed would've probably made it inescapable for most people like me, who randomly got your videos recommended. Good video still, but could be improved.
Only to make more people interested in the topic, of course, because those who know about it would watch you anyway, but still.
your website doesnt work
I actually am making a game and I always compile in O3
I have no problem using soft soft, I just dont understand the tools and such, ofc it takes a long "#"¤ ti to make sotNice tutorialng because of
woah!! Adding this
```
[profile.dev]
opt-level = 1
[profile.dev.package."*"]
opt-level = 3
```
to my cargo.toml file was an instant ~5x speed boost while running tests. Thank you much much!
maybe its just a lil *rust*y
why does my programming language need a package manager and profiles
i mean no one is forcing you to use cargo
because they’re useful (and optional)
Why would anyone choose to not use these tools when they're provided? C is horrible in this regard.
“why does my programming language need a pre-made compiler when I can implement the spec myself”
"Why can't I make things more difficult for myself!?"
YOU'RE SO LOUD HOLY MOLY
... You can change the volume on your end
@@erandom2635 I believe you misunderstood the point of my comment
but that's literally just 03 optimizations...?
Yes and? Thats the whole point, showing how to use optimization in Rust
@@NabekenProG87 isn't there directly an 03 flag in rust? also how do people not know such a basic feature.... idk it feels like pointing out the obvious...
@@snesmocha Not everyone has been programming for years, people may get started with rust or come from languages like java
You'd be surprised how many people don't understand compiler optimisations, especially people who use IDEs that hide all this information behind a debug/release dropdown menu.
@@diadetediotedio6918 I think this discussion is completely out of topic for this video, but I do think IDEs hide a bit TOO much to the point where working around one feels like black magic. Doesn't help much then that IDE skills are generally not easy to transfer between IDEs (key exception being JetBrains' products). if I need to change a compiler configuration, I want to google "how to change compiler configuration in language x", not "how to change compiler configuration in language x in IDE y", especially if the language x in question is even somewhat obscure.
Go has this too, with -ldflags="-s -w" (these remove the debug crap)