On Fri, Jul 22, 2011 at 3:03 AM, Zygmunt Krynicki <zygmunt.kryni...@canonical.com> wrote: > While I appreciate your enthusiasm and desire to fix this I have a few
Actually, I don't have much of either. But thanks for your appreciation. :) > 1) Unless I missed something your implementation always reads the whole database file, I would rather avoid that. That's actually what makes it fast, so you should not avoid it. With non-SSD one seek takes roughly the same amount of time as reading sequentially a few MB; with SSD, it's fast anyway. GDBM has to optimize behind the scenes to also read and cache the whole thing. (If it doesn't, then that's what is slow.) > 2) The similar result search you employed is much weaker than the one used by current implementation, you do not look for any permutations of the input string, just for substrings. Look again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/598282 Title: command-not-found slow for its task To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/598282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
