Proposed tag restructuring: performance-tuning and speed

Question

There are two tags, performance-tuning and speed that by present tag wiki are essentially duplicates:

• Questions about optimizing code for faster results, or how to do faster computations.

• Questions on optimizing Mathematica code for higher performance. This may mean faster execution, lower memory usage, or both. Use mathematical-optimization instead for minimization/maximization of objective functions.

I realize that performance-tuning covers more than speed alone. Perhaps every question with that tag should be co-tagged with either memory or speed. (Or some other performance aspect.) If this is what you prefer post it as an answer please. For my proposal see my own answer.

Answer 1

Co-tagging with speed or memory is what I would suggest.

---

I think internal-function-performance is borderline micro-tagging, which will quickly become impractical (we're starting to have way too many micro tags). More importantly, the tag will not be allowed by the system since it is 29 characters in length. The max allowed is 25.

Answer 2

I propose redefining speed to be used for questions about the speed of existing Mathematica functions, rather than about performance tuning. This is how I have subconsciously using the tag. A question could still be co-tagged with both, but rather than the implication of performance-tuning-for-speed it would mean that the question was about both the specific performance of Mathematica internal functions, and how to optimize code.

Arguably it would be more descriptive and broad to use something like performance or internal-function-performance instead of speed but it doesn't seem better in practice. Please comment with thoughts on this matter.