Thanks Michael, this will be very handy!
I'm testing a dbus-based service that is starting on demand and exits
after 60 seconds of inactivity. This makes it possible to get rid of
"cold cache" issue. As a second step the now-trivial client can be
rewritten in vala and linked statically to get fast
@Zygmunt: You can run:
echo 3 > /proc/sys/vm/drop_caches
to get a cold disk cache again. On my (relatively new) system the time after
that is:
$ time /usr/lib/command-not-found foobar
real0m1.851s
user0m0.208s
sys 0m0.144s
--
command-not-found should print something on the console
I think it's fairly easy to implement. We could set up a timer that goes
of after 0.5 seconds from python startup and print something like
"Searching... please wait". I'd love to implement this.
BTW: Does anyone know how to simulate "cold" storage reliably? I'd like
to fine-tune the timer delay us
** Changed in: command-not-found (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: command-not-found (Ubuntu)
Status: New => Confirmed
--
command-not-found should print something on the console immediately
https://bugs.launchpad.net/bugs/335231
You received this bug notificatio
I support this proposal. The few seconds it takes feels like a very
long time, so an immediate feedback would give the end user a smoother
experience.
--
command-not-found should print something on the console immediately
https://bugs.launchpad.net/bugs/335231
You received this bug notification
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/23163069/Dependencies.txt
--
command-not-found should print something on the console immediately
https://bugs.launchpad.net/bugs/335231
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
