Resolve perf regression from OptionsService.options
See original GitHub issuehttps://github.com/xtermjs/xterm.js/pull/3448#issuecomment-969404249
This PR creates a significant perf decrease in common modules, which have to ask option service for options (e.g.
Inputhandler.print
alone decreases by ~20%). Reason behind: https://github.com/xtermjs/xterm.js/blob/0bc02d6838a2a75048001003617bf172efcf622b/src/common/services/OptionsService.ts#L98-L107Fix: dont use getter/setter in fast path code.
We could expose the raw object internally?
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
New integrated terminals are never GPU-accelerated #140128
Whenever the terminal.integrated.gpuAcceleration setting is changed while an integrated terminal is open, the behavior is corrected. To be a ...
Read more >How to Optimize DaVinci Resolve on Your System - YouTube
Here're what we'll be touching on: - Slowdown factors - Performance mode - Working timeline resolution - Timeline proxy mode - Using proxy ......
Read more >Simple TIP to improve DaVinci Resolve Performance by 50%
In this video, I will share a simple tip that will improve DaVinci Resolve's editing performance by 50%.... I did personally experienced ...
Read more >D42263 [ARM] Fix perf regression in compare optimization.
Fix a performance regression caused by r322737. While trying to make it easier to replace compares with existing adds and subtracts, ...
Read more >What is Performance Regression Testing? - Mabl
Performance regression testing provides feedback on how the performance of the application varies according to recent changes in ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@jaminthorns thanks for the report, you spotted a pretty nasty regression 🎉
@Tyriar My
terminal.integrated.gpuAcceleration
was unset, so it was defaulting toauto
. After playing around with that setting while I had an integrated terminal open, I discovered the actual problem, which seems to be with VS Code. I opened a ticket for that here: https://github.com/microsoft/vscode/issues/140128Looks like this issue is unrelated to my problem.