Think about efficiency from each of these viewpoint1. Program requirements. Performance is stated as a requirement far more often than is actually is a requirement. Before you invest time solving a performance problem, make sure that you're solveing a problem that needs to be solved.2. Program design. If you know that a program's size and speed are important, design the program's architecutre so that you can reasonably meet your size and speed goals. Design a performance-oriented architechture, and then set resource goals for individual subsystems , features and classes.3. Class and routine design. One key to performance that comes into play at this level is the choice of data types and algorithms, which usually affect both the memory use and the execution speed of a program.4. Operation -System Interactions. If Your Program Works with External Files, Dynamic Memory or Or Output Device, It's Probably Interacting with the Operation Ystem.5. Hardware. Sometimes The Cheapest and Best Way TO IM Prove A Program's Performance Is To Buy New Hardware.6. Code Tuning. Code Tuning. Core In Ways That Mek It Run More Efficity.
