This isn't SQL specific, but a PR whose target is improving performance should measure the performance. It can be a lot of work, especially to get a representative dataset, but it will be worth it, then you can make tweaks to maximize performance, with numbers in hand. Who knows maybe this new design has a flaw and the performance is actually worse, maybe it's better but it's not worth the change. Right now you have no idea.
- Posts
- 0
- Comments
- 184
- Joined
- 2 yr. ago
- Posts
- 0
- Comments
- 184
- Joined
- 2 yr. ago
Man I wish OmniSharp didn't suck. I built an extension with VSCode and got excited about what I could build, looked into OmniSharp again and gave up when it was crashing without me even throwing a big project at it.