4 ms·
The qualifier "micro-" is right. You have to pick the language, and design your data structures and algorithms for efficiency from the ground up. Doing that aft
by jules 11y ago
The qualifier "micro-" is right. You have to pick the language, and design your data structures and algorithms for efficiency from the ground up. Doing that after the fact is a nightmare, and downright impossible if you made the wrong language choice.
- emsy 11y agoI wanted to make a similar comment but I don't understand what you mean by language choice. In my experience broad design choices can make it different to optimize later on, if you mean that.
- mrich 11y agoChoosing Python for some memory/cache-bound program may turn out to be the wrong choice, and you need to rewrite it in C/C++.
- ska 11y agoThat isn't what "micro-" typically means in this context. You are talking about design. real micro optimization examples: order of operation in an inner loop. Changing memory alignment to facilitate vectorization, figuring out your compiler is doing something dumb and tricking it into better code generation for that area,etc. If you are looking at generated assembly, chances you are doing micro-optimization.
- deleted 11y ago[deleted]
- jules 11y agoI may have expressed myself in a confusing way, but it was in fact my intention to express that while you don't need to worry about micro-optimization up front, you do need to worry about designing for efficiency up front.
- ska 11y agoAbsolutely agreed - just don't think that describes optimization, and my comment was about optimization.