Looping:
Use xrange for looping across long ranges; it uses much less memory than range, and may save time as well. Both versions are likely to be faster than a while loop:
xrange is a generator. The performance improvement from the use of generators is the result of the lazy generation of values, means values are generated on demand. Furthermore, we do not need to wait until all the elements have been generated before we start to use them.
You can often eliminate a loop by calling map instead.
Strings:
Building up strings with the concatenation operator + can be slow, because it often involves copying strings several times. Formatting using the % operator is generally faster, and uses less memory.
For example:
If you are building up a string with an unknown number of components, consider using string.join to combine them all, instead of concatenating them as you go:
Sample code :
Here are the results for above codes:
range | xrange | list_range | list_xrange | |
real | 0m4.136s | 0m2.863s | 0m1.867s | 0m1.569s |
user | 0m3.960s | 0m2.804s | 0m1.732s | 0m1.516s |
system | 0m0.160s | 0m0.048s | 0m0.124s | 0m0.048s |
File Operation: (Ext to my previous post)
# Each call to a file’s readline method is quite slow:
# It is much faster to read the entire file into memory by calling readlines; however, this uses up a lot of RAM.
# Another approach is to read blocks of lines.
#Best of all is to use the xreadlines method of a file:
Sample Codes:
Here are the results for above codes:
readline | readlines | readblock | xreadlines | |
real | 0m9.948s | 0m13.037s | 0m9.880s | 0m9.574s |
user | 0m7.144s | 0m4.316s | 0m2.716s | 0m2.372s |
system | 0m0.332s | 0m1.092s | 0m0.404s | 0m0.328s |