And, if you sceptical about whether this will increase the performance that much (since we need to read in files to acquire md5sums anyway), here are some benchmarks for just using md5sums program (python md5 module is written in c as well):
Second run: %time md5sum core/*.py ... CPU times: user 0.00 s, sys: 0.00 s, total: 0.00 s Wall time: 0.01 s Second run: [~/qt-plugin/leo]|38> %time md5sum plugins/*.py CPU times: user 0.00 s, sys: 0.00 s, total: 0.00 s Wall time: 0.02 s First run (files not in disk cache): [src/linux-headers-2.6.24-21]|49> %time md5sum `find .` CPU times: user 0.00 s, sys: 0.00 s, total: 0.00 s Wall time: 7.47 s Second run: CPU times: user 0.00 s, sys: 0.00 s, total: 0.00 s Wall time: 0.34 s And that's 62 megs of code (linux kernel headers). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
