1berry/ruby
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

YJIT: update code optimization tips in yjit.md (#10445)

Browse Source 
* YJIT: update code optimization tips in yjit.md

* Function => method
This commit is contained in:
Maxime Chevalier-Boisvert 2024-04-03 17:28:01 -04:00 committed by GitHub
parent c7cda1ae9b
commit 571bfc7402
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/yjit/yjit.md
View File

@ -265,10 +265,12 @@ This section contains tips on writing Ruby code that will run as fast as possibl
- Avoid redefining the meaning of `nil`, equality, etc. - Avoid redefining the meaning of `nil`, equality, etc.
- Avoid allocating objects in the hot parts of your code - Avoid allocating objects in the hot parts of your code
- Minimize layers of indirection - Minimize layers of indirection
- Avoid classes that wrap objects if you can - Avoid writing wrapper classes if you can (e.g. a class that only wraps a Ruby hash)
- Avoid methods that just call another method, trivial one-liner methods - Avoid methods that just call another method
- Try to write code so that the same variables always have the same type - Ruby method calls are costly. Avoid things such as methods that only return a value from a hash
- CRuby method calls are costly. Avoid things such as methods that only return a value from a hash or return a constant. - Try to write code so that the same variables and method arguments always have the same type
- Avoid using `TracePoint` as it can cause YJIT to deoptimize code
- Avoid using `Binding` as it can cause YJIT to deoptimize code
You can also use the `--yjit-stats` command-line option to see which bytecodes cause YJIT to exit, and refactor your code to avoid using these instructions in the hottest methods of your code. You can also use the `--yjit-stats` command-line option to see which bytecodes cause YJIT to exit, and refactor your code to avoid using these instructions in the hottest methods of your code.