Mailinglist Archive: opensuse-gnome (124 mails)
| < Previous | Next > |
[opensuse-gnome] [Fwd: Re: beagle bits ...]
- From: Michael Meeks <michael.meeks@xxxxxxxxxx>
- Date: Fri, 09 Jan 2009 14:08:11 +0000
- Message-id: <1231510091.14172.74.camel@linux-ko9g>
So, Morten said I could forward this.
I think it's a highly useful data-point for hacker adoption.
I imagine indexing .c files is a waste of time with beagle, it's for
documents - and worse huge, deep source code directory hierarchies -
just loading all those dentries & inodes blows your cache and makes
~everything else apparently 'slow'. Until we get a better underlying fs
this will always be a problem I think [ btrfs ].
eg. my $ time ls -Rl ~/kde/sources - took:
real 2m11.770s
user 0m0.928s
sys 0m3.824s
I guess we need a feature to prune all sub-directories of things that
look like top-level source-code / project directories. Should prolly get
that into FATE.
HTH,
Michael.
--
michael.meeks@xxxxxxxxxx <><, Pseudo Engineer, itinerant idiot
I think it's a highly useful data-point for hacker adoption.
I imagine indexing .c files is a waste of time with beagle, it's for
documents - and worse huge, deep source code directory hierarchies -
just loading all those dentries & inodes blows your cache and makes
~everything else apparently 'slow'. Until we get a better underlying fs
this will always be a problem I think [ btrfs ].
eg. my $ time ls -Rl ~/kde/sources - took:
real 2m11.770s
user 0m0.928s
sys 0m3.824s
I guess we need a feature to prune all sub-directories of things that
look like top-level source-code / project directories. Should prolly get
that into FATE.
HTH,
Michael.
--
michael.meeks@xxxxxxxxxx <><, Pseudo Engineer, itinerant idiot
--- Begin Message ---Beagle...
- From: "Morten Welinder" <mortenw@xxxxxxxxx>
- Date: Thu, 8 Jan 2009 10:13:09 -0500
- Message-id: <118833cc0901080713rc6f233bh78d379db67c68239@xxxxxxxxxxxxxx>
Here's what happens: I install a new OS and log in. Then I start
poking around and see what is broken. Typically that's a pile of
things basically having to do with having to install more software:
tex, gcc, libtool, intltool, gnome-common, autoconf, automake,
irssi, locate, bison, flex, goffice-devel, privoxy
I don't quite have that down as an artform yet, but while I am poking
around, I notice that the system is sluggish. "Beagle!" I think, and
erase it (and kill it). Then things are back to normal.
My home directory has piles of photos and piles of source trees,
some compiled, some not. There is no mail.
Also, I wonder if in fact you were hurt by the system beagle thingit
that builds a shared index for system level files, AFAIR it used to run
shortly after install, or the user process.
There was some package installed with a name that suggested it has all
the system files indexed.
I think it all basically comes down to disk seek times. My hard disk
is not particularly fast. Running at low priority probably does what it
is supposed to do as far as cpu usage is concerned. However, I
thinks its disk accesses are interacting badly with me running things
like Mozilla.
Oh, and since I don't store mail locally, I decided long ago that Beagle
doesn't give me anything that grep or git-grep doesn't do better. That
certainly lowers my tolerance too.
Morten
--- End Message ---
| < Previous | Next > |