Should we not use a feature in code because of its slowness, or hope that the promise of that feature and its convenience matches our expectations for performance some day?
-
-
Replying to @buhakmeh
It's always a trade off. How high on the priority list is performance? Can you tolerate the speed increase to just get it implemented? I have found that often a single feature doesn't make or break performance, it is usually something else.
2 replies 0 retweets 0 likes -
Replying to @phillipsj73
As developers (and users) we want it all. Once we get it working, we want it faster :)
1 reply 0 retweets 1 like -
Replying to @buhakmeh
When I want better performance I break out dotTrace and dotMemory to find high value areas and go from there. We can never have it all because sometimes what's needed for performance doesn't align with other goals.
1 reply 0 retweets 1 like -
Replying to @phillipsj73
I try to do that to, but honestly sometimes I'm not sure what I'm looking for.
1 reply 0 retweets 0 likes -
Replying to @buhakmeh
It's like SQL explain plans. You just have to use the Force.
1 reply 0 retweets 0 likes -
Replying to @phillipsj73
I'd love a Profiler workshop. Bring your code and see what we find. Not sure why
@jetbrains doesn't offer those.3 replies 0 retweets 1 like
Thanks. We will share with our team.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.