<div dir="ltr">I not search things all the time, but when I do I use find-pipe-grep. Not because "locate" is an inferior solution, not at all, just a matter of habit.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, May 22, 2019 at 5:09 PM Andrea Corbellini <<a href="mailto:corbellini.andrea@gmail.com">corbellini.andrea@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">On Wed, May 22, 2019 at 8:47 PM Julian Andres Klode <<a href="mailto:julian.klode@canonical.com" target="_blank">julian.klode@canonical.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, May 22, 2019 at 01:19:48PM -0600, Neal McBurnett wrote:<br>
> I use mlocate multiple times a day.<br>
> Find is way too slow and inconvenient for finding files in a big<br>
> set of filesystems, compared to properly configuring mlocate.<br>
<br>
Specifically, the filesystem must be huge or on a slow medium. It might make<br>
sense to move it out of standard and elsewhere, as I don't think it's<br>
necessarily needed everywhere, such as laptops.<br></blockquote><div><br></div><div>There's also the case of a blazing-fast medium, but high I/O load.</div><div>That's the case that I'm often facing when working on production servers. Using find there is very frustrating.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Consider my laptop, fairly standard, 512 GB NVME SSD, about 250G allocated,<br>
containing about 1435134 files. mlocate foo takes 1s, find / -mount<br>
-name '*foo*' takes about 7-9 secs, or 19 seconds with all mount points <br>
(but there is a davfs mount of an internet server, so things might be<br>
screwed up a bit).<br>
<br>
19s to find something is perfectly workable, also you don't usually<br>
find from /, but you have an idea where things are, so it will be much<br>
faster.<br></blockquote><div><br></div><div>19s for my standards are a lot, especially if I have to do multiple searches.</div><div>There have been cases where I dumped the output of "find /" into a file and resorted to search using grep.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
I think mlocate only really makes sense on data storage servers with<br>
huge disks, or on machines with HDDs. I therefore do not think the<br>
overhead of building the index is warranted for most users. It might<br>
make sense to keep mlocate in always-on tasks, like servers, but get<br>
rid of it from desktop scenarios.<br>
-- <br>
debian developer - <a href="http://deb.li/jak" rel="noreferrer" target="_blank">deb.li/jak</a> | <a href="http://jak-linux.org" rel="noreferrer" target="_blank">jak-linux.org</a> - free software dev<br>
ubuntu core developer i speak de, en<br>
<br>
-- <br>
ubuntu-devel mailing list<br>
<a href="mailto:ubuntu-devel@lists.ubuntu.com" target="_blank">ubuntu-devel@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel</a><br>
</blockquote></div></div>
-- <br>
ubuntu-devel mailing list<br>
<a href="mailto:ubuntu-devel@lists.ubuntu.com" target="_blank">ubuntu-devel@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature">Marcos H. Alano<br>Linux System Administrator<br><a href="mailto:marcoshalano@gmail.com" target="_blank">marcoshalano@gmail.com</a></div>