3 ms·
Why is this considered a "bug"? It might be a little slower in some cases, but of the behavior is correct for a set of inputs and outputs, the classification i
by metadat 4y ago
Why is this considered a "bug"? It might be a little slower in some cases, but of the behavior is correct for a set of inputs and outputs, the classification is a stretch.
- ncmncm 4y agoIt is a bug that costs you extra money. Makes extra revenue for Azure, though, so there's that.
- brucedawson 4y agoCorrectness bugs are just one type of bug. Performance bugs are another type. The designation of what should be counted as a bug is less clear for performance bugs but if some operation is slower than it could/should be, and if this slowdown is significant enough to matter, and if fixing the slowdown is quite practical then, yeah, I would definitely call it a bug. I have filed many bug reports for performance issues over the years, and many of them have been addressed.
- eru 4y agoIn the extreme: a computer that runs 0.1% as slow as it's supposed to might as well be crashed.
- dspillett 4y agoOften performance is a feature. In those cases, bad performance is a fault.
- ArrayBoundCheck 4y agoI'd say something unintentional is a bug. Perhaps someone can use this in a DoS attack