Changes between Version 76 and Version 77 of DeveloperGuidelines/Optimisation


Ignore:
Timestamp:
12/04/11 10:21:05 (13 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • DeveloperGuidelines/Optimisation

    v76 v77  
    1717 * If Python is eating too much memory, it could be because you are instantiating lots of a particular class, consider using !__slots!__ http://stackoverflow.com/questions/472000/python-slots
    1818 * You can check the actual memory usage per class using !MyClass.!__basicsize!__, remembering that subclasses of classes without !__slots!__ or top-level classes without !__slots!__ have a !__dict!__ which also takes up memory.
     19 * Commercial tool with free trial: http://newrelic.com/python
    1920 * If a specific inner-loop routine cannot be optimised in Python, then consider writing a C routine for this use case.
    20 
    2121 ''You can't beat C with Python, unless it's about readability.''
    2222=== !JavaScript ===