Code review comment for lp://qastaging/~fahlgren/command-not-found/speedup
Revision history for this message
| Daniel Fahlgren (fahlgren) wrote | # |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
To get some better statistics did I run 100 calls to command-not-found for different commands.
For the missing command "cab"
On my i5@2.30GHz with a SSD disk is the execution time dropped from 12.362s to 6.888s.
On my Atom 330 with a 2.5" mechanical disk is the execution time dropped from 1m12.961s to 38.413s
For the missing command "emacx"
On my i5@2.30GHz is it dropped from 12.749s to 6.933s
Om my Atom 330 is it dropped from 1m13.722s to 39.194s
For the missing command "empathy-debuggert"
On my i5@2.30GHz is it dropped from 13.678s to 7.873s
Om my Atom 330 is it dropped from 1m20.910s to 46.375s
These numbers does include the time for bash to iterate 100 times and do the calls. The output was discarded to /dev/null not to interfere with the results.