As and software producer all of us want to do is software product with correct functionality. Is that enough ? No. We need to give product with correct functionality with optimum resource consumption as well.
Today I'm going to tell you some tips and trikes about resource optimization. basically it is about Memory and CPU resources.
1. Switch for multiple If
When you are using multiple If conditions ( Most of the time more than 2 ) CPU (Registry level) instructions check as far as use much If with code. It consume more registers in CPU. But with switch it just use check and Jump CPU instruction that far more faster than assignments. Using jump tables makes switches much faster than some if-statements
Use switch when ever possible once you find more than two if statements.
2. Use structures according to the situation
Execution of class is much more consume resources than class. Whenever you don't need to use functions bind with objects and when you don't go with boxing and unboxing much with code.
3. Chunky calls
Don't let your functions to handle lot of task by itself. use modularity to avoid it.
4. Add Collections
Never try to assign collection items one by one to the another collection. Just try to use simple casting and try to add entire collection directly.
5. Working with strings.
When you are working with string most of the cases we try to concatenate string by '+'operator.(including me ). But sad story is there is more optimal solution than that. use string bulider to concatenate strings.
Here for start.
6. Use bits whenever as possible.
I saw most of the programmers use integers/strings to hold the simple states, flags. Please don't do that there is more than 2 states. Just use bit or bool to store states. It will optimize code and resource as well. ( Simply bit is smaller than more bits)
7. Array as possible
When we use simple basic array it will helpful to maintain machine instructions(registry). Other collections need more than array because most of them are derived form it. Array is basic element in modern machine instructions.
8. ObservableCollection vs List
Use List whenever that your items not binded with the UI. Observation collections are derived from List and it also holds the property changed notifications. If there is no use of property change go for List. ObservableCollection check the property change when it on use and because of that it consume more.
9. For than foreach
Use while, for and do while loops wherever than foreah. foreach has good performance but basic loops are better than it.
10. ToString
Some programmers use ToString method wherever elements are already strings. Use ToString wherever the element that con the string. don't use ToString as habit. With integers use
ToStringLookup will optimize memory heap that using with converting integer.
11. Don't sort collections already sorted.
Check collection already sorted or not before sort it.
12. Global variables.
Use global variables when you using same type of object frequently
13. Constant and static
Constants are not assignable memories but they are easy to load.
Static is more faster than instant creations. When load statics no need of run time to check the instance
Hope this is helps...
