Changes between Version 72 and Version 73 of DeveloperGuidelines/Optimisation

Timestamp:

11/18/11 12:24:08 (13 years ago)

Author:

Mike A

Comment:

escaping markup

DeveloperGuidelines/Optimisation

@@ -16 +16 @@
  * http://diveintopython.org/performance_tuning/index.html
  * If a specific inner-loop routine cannot be optimised in Python, then consider writing a C routine for this use case.
- * 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 
- * 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.
+ * 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 
+ * 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.
 
  ''You can't beat C with Python, unless it's about readability.''