From: Matthias Bethke <matthias@towiski.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Beagle eating up Resources!! (BEagled-index-helper)
Date: Wed, 28 Feb 2007 23:25:55 +0100 [thread overview]
Message-ID: <20070228222555.GI4105@huxley> (raw)
In-Reply-To: <1172570953.32328.104.camel@neuromancer.home.net>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
Hi Ow,
on Tuesday, 2007-02-27 at 18:09:13, you wrote:
> Does anyone here knows if beagle really sucks up resources?? I just
> emerged it a week ago and I'm getting very pissed off at it as it's
> using a lot of resources. The laptop doesn't get much idle time.
I was under the impression that this was its raison d'être...?
An Apache project perpetr^Wported to .NET can't be anything but a
resource hog. It looked pretty interesting when they included it with
the SuSE we use @work so it got installed on a few boxes, but seeing
what it did to these 2800 MHz P4s put it on top of the list of things to
be disabled before rollout.
cheers!
Matthias
--
I prefer encrypted and signed messages. KeyID: FAC37665
Fingerprint: 8C16 3F0A A6FC DF0D 19B0 8DEF 48D9 1700 FAC3 7665
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-02-28 22:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 10:09 [gentoo-user] Beagle eating up Resources!! (BEagled-index-helper) Ow Mun Heng
2007-02-27 12:06 ` Jürgen Geuter
2007-02-27 13:21 ` Kristian Poul Herkild
2007-02-27 13:41 ` Jürgen Geuter
2007-02-28 9:30 ` Ow Mun Heng
2007-02-28 21:28 ` Roy Wright
2007-02-28 23:50 ` Kent Fredric
2007-03-01 0:26 ` Albert Hopkins
2007-03-01 0:54 ` Ow Mun Heng
2007-03-01 14:10 ` Roger Mason
2007-03-04 1:16 ` Alan E. Davis
2007-02-27 13:18 ` Kristian Poul Herkild
2007-02-28 22:25 ` Matthias Bethke [this message]
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=20070228222555.GI4105@huxley \
--to=matthias@towiski.de \
--cc=gentoo-user@lists.gentoo.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