4 ms·
If you can't measure (very well?), how would you know the improvement in a certain use-case exists or not?
by mfukar 9y ago
If you can't measure (very well?), how would you know the improvement in a certain use-case exists or not?
- userbinator 9y agoIndeed. If you can't really measure the difference, then I'd say setting it either way probably doesn't matter anyway.
- dboreham 9y agoMore like : if you can't measure the difference then definitely turn it off because if it is on there is a non-zero chance of significant instability events in your future.
- brazzledazzle 9y agoIf I'm understanding their comments correctly it's because the downside isn't just a possible not-increase/decrease in performance it's instability and unpredictable behavior. I worry that it could translate into those vague and difficult to reproduce "the application is weird/slow" reports. Of course you could profile and measure performance to determine if the warning is applicable but is that something I should be doing for every part of the stack? I should but should I prioritize that over x, y or z?