git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Applying git technology to fix the locate command

From
jonsmirl@gmail.com <jonsmirl@gmail.com>
Date
Oct 7, 2012, 19:18 UTC
Message-ID
<CAKON4OwRuEhaHhCkv6oS+wL1NEp-3DyWcYbRqq5=RKuqgs8f0g@mail.gmail.com>
In-Reply-To
<CAKON4OzyAt-e0Ygj=7+Ze7ywU+RNTsi-Nn5huCnEWy8o=a-EUA@mail.gmail.com>

I played around with updatedb.conf to exclude .git files and my /exports directory. I got the db down to 136MB and 4.5s for a null search. This command still needs help. Given that I have the entire db file cached it should be able to respond instantly on a null search.

-- 
Jon Smirl
jonsmirl@gmail.com
Previous: jonsmirl@gmail.com
Message 2 of 2 in “Applying git technology to fix the locate command”
  1. jonsmirl@gmail.comOct 7, 2012
  2. jonsmirl@gmail.comOct 7, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.