Changes between Version 21 and Version 22 of DeveloperGuidelines/Optimisation
- Timestamp:
- 05/13/10 19:15:06 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DeveloperGuidelines/Optimisation
v21 v22 9 9 * http://www.skymind.com/~ocrow/python_string/ 10 10 * http://diveintopython.org/performance_tuning/index.html 11 * If a specific inner-loop routine can ot be optimised in Python, then consider writing a C routine for this use case.11 * If a specific inner-loop routine cannot be optimised in Python, then consider writing a C routine for this use case. 12 12 13 13 1. Optimize the models, throw away what we don't need. Every field counts.[[BR]]Especially problematic in view of performance are references (joins), as they execute implicit DB requests. The more complex references are, the slower the model loads. … … 27 27 28 28 There are more things to consider besides performance, e.g. usability and maintainability of code. New contributors should be able to easily understand the code, and bugs should be easy to find. 29 30 Python performance tips: http://wiki.python.org/moin/PythonSpeed/PerformanceTips 29 31 30 32 === Specific Examples === … … 48 50 }}} 49 51 (0.012 vs. 0.007 seconds vs in a test case) 52 53 Javascript string concatenation: http://aymanh.com/9-javascript-tips-you-may-not-know#String_Concatenation_vs._Array.join 50 54 51 55 === Profiling ===