Changes between Version 21 and Version 22 of DeveloperGuidelines/Optimisation


Ignore:
Timestamp:
05/13/10 19:15:06 (12 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DeveloperGuidelines/Optimisation

    v21 v22  
    99 * http://www.skymind.com/~ocrow/python_string/
    1010 * http://diveintopython.org/performance_tuning/index.html
    11  * If a specific inner-loop routine canot 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.
    1212
    1313 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.
     
    2727
    2828There 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
     30Python performance tips: http://wiki.python.org/moin/PythonSpeed/PerformanceTips
    2931
    3032=== Specific Examples ===
     
    4850}}}
    4951(0.012 vs. 0.007 seconds vs in a test case)
     52
     53Javascript string concatenation: http://aymanh.com/9-javascript-tips-you-may-not-know#String_Concatenation_vs._Array.join
    5054
    5155=== Profiling ===