[2023-02-13] Performance Team Demo #5642
Replies: 5 comments
-
Based on the Feb 6 Demo review feedback individual issues were reported and are being worked on:
Low priority tasks reported:
Custom Hashing has been fully integrated :
We can move forward and bugfix and speed up. |
Beta Was this translation helpful? Give feedback.
-
Last week, the frontend parser transition landed (#4113). This is what startup looked like before (opening "Orders", zoomed to the part after we receive project source code from the LS): The circled portion is over 500ms of CPU work in Since then I've been working on optimizing shader compilation scheduling (#5606). I'll finish that today. Next I'll profile some objectives #5603 and look for the next optimization. |
Beta Was this translation helpful? Give feedback.
-
Spent much time on Still, things are getting worse when they are not: Tried to fix that, but this is extremely not easy. However, after a talk with @wdanilo we decided, that the normal shapes, if not aligned to pixels, are bad anyway, and we rather aim to snap things to pixels if they are not moving. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Let me start! :)
I was working on improving the Electron integration, this involves:
The PR is opened, still not all code cleaned, will be cleaned for tomorrow: #5633
As a result, we've got Electron app working on M2 Macs (not crashing anymore, I hope). Also, it should remove some of community issues, including this one: #3801
As a side improvement, the command line interface is way nicer now, here is the screenshot of running the electron app with
-help
command (not all switches are visible, as we have almost a 100 switches now, including chrome/electron switches to debug the app).Beta Was this translation helpful? Give feedback.
All reactions