linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
Date: Tue, 19 Jan 2016 07:28:44 -0500	[thread overview]
Message-ID: <569E2BFC.8080107@gmail.com> (raw)
In-Reply-To: <pan$85c04$d9fd4f4d$1304efda$85c18be@cox.net>

On 2016-01-19 04:14, Duncan wrote:
> Oh, I also don't allow any crazy indexers, like kde's baloo or the older
> updatedb for (s)locate, to go crazy indexing everything, thereby wasting
> valuable cache memory on files I won't actually be using.  These things
> get shut down as soon as I discover new ones, and preferably get
> uninstalled, with dependencies on them turned off (on gentoo, via
> appropriate USE flag) as well.  On kde4 I was even carrying my own no-
> semantic-desktop patches for awhile, when gentoo/kde decided they weren't
> going to support kde without semantic-desktop.  Fortunately they changed
> their minds.  I'm now finally updated to kde-frameworks5 with plasma5,
> and have baloo installed for that as I don't yet grok how to keep it off
> the system entirely in frameworks/plasma5, but it's definitely shut down
> as far as runtime goes.
There's a reason I don't use KDE...
(Well, a couple actually, the indexing getting pulled in is only part of 
it, I also dislike the all-or-nothing packaging (everything seems to 
depend on everything else), and having to update the whole thing in 
lock-step; somewhat ironically, GNOME has the same issues these days, so 
I don't use that either).

That aside, it's probably worth noting that updatedb used by 
{,m,s}locate only indexes metadata, and it does so a lot more 
efficiently than most of the desktop search-engine indexers out there, 
so it's not quite as bad as baloo or tracker or some of the other 
options.  Unlike those, updatedb pretty much just calls stat on 
everything it's told to index, which takes time, but is not particularly 
bad for your cache if you're just running it on your home directory.
>
> There is a package indexer that runs, and of course syncing package
> updates loads all that in cache, but all that's on my packages partition,
> unmounted when I'm not actively doing package updates, etc, thereby
> freeing the package updates subsystem caches.
For those who might be interested, autofs is wonderful for handling 
stuff like this.


  reply	other threads:[~2016-01-19 12:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-16 12:27 Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls Al
2016-01-16 14:10 ` Duncan
2016-01-16 18:07   ` Rich Freeman
2016-01-18 12:23     ` Austin S. Hemmelgarn
2016-01-23 22:22       ` Mark Fasheh
2016-01-20 14:49     ` Al
2016-01-20 14:43   ` Al
2016-01-21  8:23     ` Qu Wenruo
2016-01-21 14:53       ` Al
2016-01-21 17:23         ` Chris Murphy
2016-01-22 11:33           ` Al
2016-01-23  2:44             ` Chris Murphy
2016-02-02  2:55             ` Qu Wenruo
2016-01-18  1:36 ` Qu Wenruo
2016-01-18  3:10   ` Duncan
2016-01-18  3:16     ` Qu Wenruo
2016-01-18  3:51       ` Duncan
2016-01-18 12:48         ` Austin S. Hemmelgarn
2016-01-19  8:30           ` Duncan
2016-01-19  9:14             ` Duncan
2016-01-19 12:28               ` Austin S. Hemmelgarn [this message]
2016-01-19 15:40                 ` Duncan
2016-01-20  8:32                 ` Brendan Hide
2016-01-19 12:21             ` Austin S. Hemmelgarn
2016-01-20 15:12               ` Al
2016-01-20 18:21                 ` Duncan
2016-01-20 14:53   ` Al

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=569E2BFC.8080107@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).