-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Randall R Schulz schreef:
> On Sunday 13 January 2008 11:07, Randall R Schulz wrote:
>>
>>
>> So a program like the Beagle indexer has to be smart enough about the
>> load it offers to get its work done as quickly as possible without
>> interfer
Kevin Dupuy wrote:
On Mon, 2008-01-14 at 22:30 +0200, Alexey Eremenko wrote:
Yes, BTW, beagle is eating my CPU too... and I really would like to
see this feature _disabled by default_ in the upcoming openSUSE 11.0.
--
-Alexey Eremenko "Technologov"
As has been said before, that is something th
On Mon, 2008-01-14 at 22:30 +0200, Alexey Eremenko wrote:
> Yes, BTW, beagle is eating my CPU too... and I really would like to
> see this feature _disabled by default_ in the upcoming openSUSE 11.0.
>
> --
> -Alexey Eremenko "Technologov"
As has been said before, that is something that a BUG nee
On Mon, 2008-01-14 at 06:03 -0500, Aaron Kulkis wrote:
> Rajko M. wrote:
> > On Monday 14 January 2008 02:22:18 am Clayton wrote:
> >
> >> I see a few people here saying Beagle runs fine for them with no
> >> noticeable impact on performance... how?
> >
> > It seems that you monitor Beagle in a f
On Mon, 2008-01-14 at 12:35 +0100, Clayton wrote:
> > > I see a few people here saying Beagle runs fine for them with no
> > > noticeable impact on performance... how?
> >
> > It seems that you monitor Beagle in a first time after installation.
> > Though there is pops up note telling that computer
On Mon, 2008-01-14 at 03:57 -0500, Aaron Kulkis wrote:
> Clayton wrote:
> >>> Anyone else seeing Beagle really kill performance? I have disabled
> >>> it and my machine finally is perky, but every now and then, I find it
> >>> in memory again. How do I arange it to chew up less memory and CPU o
Yes, BTW, beagle is eating my CPU too... and I really would like to
see this feature _disabled by default_ in the upcoming openSUSE 11.0.
--
-Alexey Eremenko "Technologov"
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Monday 14 January 2008 05:35:30 am Clayton wrote:
> > > I see a few people here saying Beagle runs fine for them with no
> > > noticeable impact on performance... how?
> >
> > It seems that you monitor Beagle in a first time after installation.
> > Though there is pops up note telling that compu
On Monday 14 January 2008 05:03:11 am Aaron Kulkis wrote:
> Rajko M. wrote:
> > On Monday 14 January 2008 02:22:18 am Clayton wrote:
> >> I see a few people here saying Beagle runs fine for them with no
> >> noticeable impact on performance... how?
> >
> > It seems that you monitor Beagle in a firs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Monday 2008-01-14 at 12:35 +0100, Clayton wrote:
I let Beagle run longer than 24h on the dual core system. System
response remained horrible. A friend installed 10.2 and then updated
everything including Beagle... it ran for a couple of week
Rajko M. wrote:
On Monday 14 January 2008 02:22:18 am Clayton wrote:
I see a few people here saying Beagle runs fine for them with no
noticeable impact on performance... how?
It seems that you monitor Beagle in a first time after installation.
Though there is pops up note telling that comput
Clayton wrote:
Anyone else seeing Beagle really kill performance? I have disabled
it and my machine finally is perky, but every now and then, I find it
in memory again. How do I arange it to chew up less memory and CPU or
kill it once and for all?
Usually this indicates you have a problemati
> > I see a few people here saying Beagle runs fine for them with no
> > noticeable impact on performance... how?
>
> It seems that you monitor Beagle in a first time after installation.
> Though there is pops up note telling that computer will be slower in a first
> few minutes. Later on you shoul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Monday 2008-01-14 at 09:22 +0100, Clayton wrote:
Usually this indicates you have a problematic file (usually its broken
or corrupt) that causes the index helper to go into a loop while
indexing.
See http://beagle-project.org/Troubleshooting_C
On Monday 14 January 2008 02:22:18 am Clayton wrote:
> I see a few people here saying Beagle runs fine for them with no
> noticeable impact on performance... how?
It seems that you monitor Beagle in a first time after installation.
Though there is pops up note telling that computer will be slowe
> > Anyone else seeing Beagle really kill performance? I have disabled
> > it and my machine finally is perky, but every now and then, I find it
> > in memory again. How do I arange it to chew up less memory and CPU or
> > kill it once and for all?
>
> Usually this indicates you have a problema
On Sunday 13 January 2008 11:07, Randall R Schulz wrote:
>
>
> So a program like the Beagle indexer has to be smart enough about the
> load it offers to get its work done as quickly as possible without
> interfering with interactive use.
By the way, I'm not saying I think Beagle does (or does
On Saturday 22 December 2007 09:49, Aaron Kulkis wrote:
> Joe Sloan wrote:
> > ...
> >
> > If you look at boinc, it's possible to do this with clever
> > programming, completely in userland. When we've run boinc, the load
> > average on the box rises to the point that you'd think the box is
> > in
Joe Sloan wrote:
Aaron Kulkis wrote:
Sloan wrote:
Gary Baribault wrote:
And just for your general information, with Beagle installed, SuSE was
using 1.5Gig of Memory and 256Meg of Swap.
After removing Beagle and a reboot, I have 887Meg free and no swap used,
I would think that Beagle qualifie
Kevin Dupuy wrote:
On Mon, 2007-12-17 at 10:53 -0500, Aaron Kulkis wrote:
Gary Baribault wrote:
Hi all,
Anyone else seeing Beagle really kill performance? I have disabled
it and my machine finally is perky, but every now and then, I find it
in memory again. How do I arange it to chew up le
Anders Johansson wrote:
On Sunday 23 December 2007 01:26:08 Carlos E. R. wrote:
The Saturday 2007-12-22 at 18:09 +0100, Anders Johansson wrote:
Actually, it helps solve it, sometimes. The application crashes,
probably
I wouldn't say "probably". It shouldn't be par for the course for an
applica
On Sunday 23 December 2007 01:26:08 Carlos E. R. wrote:
> The Saturday 2007-12-22 at 18:09 +0100, Anders Johansson wrote:
> >> Actually, it helps solve it, sometimes. The application crashes,
> >> probably
> >
> > I wouldn't say "probably". It shouldn't be par for the course for an
> > application
Linda Walsh wrote:
Aaron Kulkis wrote:
I just checked the man page for ulimit, and did a search
for the string "swap" and it came up empty... so it looks
like ulimit might not help herealthough ulimit -v can set
an upper limit on virtual memory,
---
You want to cap virtual memory usage
Linda Walsh wrote:
The Saturday 2007-12-22 at 16:06 +0100, Anders Johansson wrote:
The real solution here is to find and fix the bug that causes
beagle to
allocate so much memory. It doesn't happen on all systems.
---.
Without question, this is the best solution.
Anders Johansson wro
> Beagle should be scrapped and started over from the
> ground up, starting with the design assumption that it
> is to behave as an unobtrusive background process, not
> the current one which can take over the whole system
> with a "feed me" attitude as if the whole purpose for
> a computer and its
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Saturday 2007-12-22 at 16:29 -0800, Linda Walsh wrote:
..
This is why I made a comment about *not* using "swap"
on a system -- if you are using swap on any regular basis (my
threshhold is using swap, *anytime*, during 'normal' day-to-
On Saturday 22 December 2007 07:29:04 pm Linda Walsh wrote:
> >>> The Saturday 2007-12-22 at 16:06 +0100, Anders Johansson wrote:
> The real solution here is to find and fix the bug that causes beagle
> to allocate so much memory. It doesn't happen on all systems.
>
> ---.
> Without
Aaron Kulkis wrote:
I just checked the man page for ulimit, and did a search
for the string "swap" and it came up empty... so it looks
like ulimit might not help herealthough ulimit -v can set
an upper limit on virtual memory,
---
You want to cap virtual memory usage, since
virtual
The Saturday 2007-12-22 at 16:06 +0100, Anders Johansson wrote:
The real solution here is to find and fix the bug that causes beagle to
allocate so much memory. It doesn't happen on all systems.
---.
Without question, this is the best solution.
Anders Johansson wrote:
I wouldn't sa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Saturday 2007-12-22 at 18:09 +0100, Anders Johansson wrote:
Actually, it helps solve it, sometimes. The application crashes, probably
I wouldn't say "probably". It shouldn't be par for the course for an
application to not check return value
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Linda Walsh <[EMAIL PROTECTED]> [12-22-07 18:18]:
> I just checked suse10.2 packages...
>
> If you have the "ionice" program (/usr/bin/ionice) installed
> under SuSE-10.3 OR -10.2, daily beagle indexing will automatically use it
> to set
Aaron Kulkis wrote:
ah... ionice seems to be a new invention.
I'll give it a try when I build a new system this month.
---
I just checked suse10.2 packages...
If you have the "ionice" program (/usr/bin/ionice) installed
under SuSE-10.3 OR -10.2, daily beagle indexing will automa
Aaron Kulkis wrote:
> And since top is trustworthy, just put a symbolic link in
> /usr/bin to the top executable.
>
> Admittedly, it's a patch up, but it's superior to playing
> around with the $PATH variable(*) all the time
>
> (*) for one, it doesn't help much for anyone who has a
> currently
Joe Sloan wrote:
Dave Howorth wrote:
Joe Sloan wrote:
in fact anything in /opt or /usr/local usually wasn't even in root's
path
I should hope not! root should have a strictly limited path to limit
security exploits.
I'm not sure the lack of finish characteristic of the old school unices
pro
Ken Schneider wrote:
Aaron Kulkis pecked at the keyboard and wrote:
Joe Sloan wrote:
root's UID.
Examples, please? What would be the security advantage of typing
"/opt/SunWzztop/bin/top" every time, instead of "top", with
/opt/SunWzztop/bin in the path?
[EMAIL PROTECTED]:~> which top
/usr/bin
Sloan wrote:
Aaron Kulkis wrote:
Joe Sloan wrote:
Examples, please? What would be the security advantage of typing
"/opt/SunWzztop/bin/top" every time, instead of "top", with
/opt/SunWzztop/bin in the path?
[EMAIL PROTECTED]:~> which top
/usr/bin/top
[EMAIL PROTECTED]:~>
Why isn't top in /us
Anders Johansson wrote:
On Saturday 22 December 2007 18:00:43 Carlos E. R. wrote:
The Saturday 2007-12-22 at 16:06 +0100, Anders Johansson wrote:
[ulimit]
The real solution here is to find and fix the bug that causes beagle to
allocate so much memory. It doesn't happen on all systems.
When i
On Saturday 22 December 2007 18:00:43 Carlos E. R. wrote:
> The Saturday 2007-12-22 at 16:06 +0100, Anders Johansson wrote:
>
> [ulimit]
>
> > The real solution here is to find and fix the bug that causes beagle to
> > allocate so much memory. It doesn't happen on all systems.
> >
> > When it happe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Saturday 2007-12-22 at 16:06 +0100, Anders Johansson wrote:
[ulimit]
The real solution here is to find and fix the bug that causes beagle to
allocate so much memory. It doesn't happen on all systems.
When it happens, a bug should be opened,
On Friday 21 December 2007 01:06:38 [EMAIL PROTECTED] wrote:
> On Thursday 20 December 2007 09:38:46 am Carlos E. R. wrote:
> > The Thursday 2007-12-20 at 09:22 -1000, [EMAIL PROTECTED] wrote:
> > > Even if one nices and ionices beagle, there still is the matter of swap
> > > space getting filled.
[EMAIL PROTECTED] wrote:
On Wednesday 19 December 2007 01:02:56 pm Aaron Kulkis wrote:
ah... ionice seems to be a new invention.
I'll give it a try when I build a new system this month.
Even if one nices and ionices beagle, there still is the matter of swap space
getting filled. Usually it
Carlos E. R. wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-20 at 09:22 -1000, [EMAIL PROTECTED] wrote:
Even if one nices and ionices beagle, there still is the matter of
swap space
getting filled. Usually it is when that happens when ugly thoughts
against
the de
Aaron Kulkis pecked at the keyboard and wrote:
> Joe Sloan wrote:
>>> root's UID.
>>
>> Examples, please? What would be the security advantage of typing
>> "/opt/SunWzztop/bin/top" every time, instead of "top", with
>> /opt/SunWzztop/bin in the path?
>
> [EMAIL PROTECTED]:~> which top
> /usr/bin/t
Aaron Kulkis wrote:
> Joe Sloan wrote:
>>
>> Examples, please? What would be the security advantage of typing
>> "/opt/SunWzztop/bin/top" every time, instead of "top", with
>> /opt/SunWzztop/bin in the path?
>
> [EMAIL PROTECTED]:~> which top
> /usr/bin/top
> [EMAIL PROTECTED]:~>
>
>
> Why isn't to
Joe Sloan wrote:
Aaron Kulkis wrote:
Joe Sloan wrote:
I had to edit the paths even more extensively in hpux, solaris or aix -
in fact anything in /opt or /usr/local usually wasn't even in root's
path
AND THEY'RE NOT SUPPOSED TO BE!!!
That's a security risk.
Root is for ADMINISTRATIVE use, n
On Wednesday 19 December 2007 04:54:01 am Linda Walsh wrote:
> Rajko M. wrote:
...
> >> ---
> >>Might try making sure the "cfq" block algorithm is being used,
> >> then set 'beagle' to run at lowest priority (nice -19
> >> beagle-start-script).
> >
> > info:nice
> > "Nicenesses range at least f
On Thursday 20 December 2007 09:38:46 am Carlos E. R. wrote:
> The Thursday 2007-12-20 at 09:22 -1000, [EMAIL PROTECTED] wrote:
> > Even if one nices and ionices beagle, there still is the matter of swap
> > space getting filled. Usually it is when that happens when ugly thoughts
> > against the d
Philip Dowie wrote:
> lets say /opt/SunWzztop/bin is not first on your path, and for some reason a
> directory in your path was writable by some malicious user - if they put a
> top in there, then all of a sudden when you type in top, expecting to get
> /opt/SunWzztop/bin/top, you get another to
does funky
stuff like rm -rf / whoops.
-Original Message-
From: Joe Sloan [mailto:[EMAIL PROTECTED]
Sent: Thursday, 20 December 2007 5:30 p.m.
To: opensuse@opensuse.org
Subject: Re: [opensuse] Beagle under 10.3 is really eating up my CPU
--snip--
>> - but I expect to spend time
all R Schulz [mailto:[EMAIL PROTECTED]
Sent: Thursday, 20 December 2007 2:36 p.m.
To: opensuse@opensuse.org
Subject: Re: [opensuse] Beagle under 10.3 is really eating up my CPU
On Wednesday 19 December 2007 16:42, Carlos E. R. wrote:
> The Wednesday 2007-12-19 at 16:29 -0800, Randall R Schu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-20 at 09:22 -1000, [EMAIL PROTECTED] wrote:
Even if one nices and ionices beagle, there still is the matter of swap space
getting filled. Usually it is when that happens when ugly thoughts against
the developers spring to lif
On Wednesday 19 December 2007 01:02:56 pm Aaron Kulkis wrote:
>
> ah... ionice seems to be a new invention.
> I'll give it a try when I build a new system this month.
Even if one nices and ionices beagle, there still is the matter of swap space
getting filled. Usually it is when that happens wh
On Wednesday 19 December 2007 23:51:42 Aaron Kulkis wrote:
> Anders Johansson wrote:
> > On Monday 17 December 2007 19:58:18 JP Rosevear wrote:
> >> Beagle already does nice itself and employ strategies for reducing work
> >> when the CPU is not idle. However I/O is a problem and non-root
> >> pro
Aaron Kulkis wrote:
> Joe Sloan wrote:
>> I had to edit the paths even more extensively in hpux, solaris or aix -
>> in fact anything in /opt or /usr/local usually wasn't even in root's
>> path
>
> AND THEY'RE NOT SUPPOSED TO BE!!!
> That's a security risk.
>
> Root is for ADMINISTRATIVE use, no
Aaron Kulkis wrote:
> Sloan wrote:
>> Gary Baribault wrote:
>>> And just for your general information, with Beagle installed, SuSE was
>>> using 1.5Gig of Memory and 256Meg of Swap.
>>>
>>> After removing Beagle and a reboot, I have 887Meg free and no swap used,
>>> I would think that Beagle qualif
Linda Walsh wrote:
Aaron Kulkis wrote:
Until they remove every trace of it from human existence,
except for snippets preserved for teaching purposes, under
the topic of "DO NOT DO THESE THINGS in a background services
programs"
---
Well it depends on your configuration, no doubt.
I saw one
Anders Johansson wrote:
On Monday 17 December 2007 19:58:18 JP Rosevear wrote:
Beagle already does nice itself and employ strategies for reducing work
when the CPU is not idle. However I/O is a problem and non-root
processes can't change their own I/O priority iirc.
Actually, they can. "All"
Joe Sloan wrote:
Aaron Kulkis wrote:
Joe Sloan wrote:
I have to fix the path to deal with the complaints of users who complain
that e.g. "ifconfig" isn't installed, or who maybe have to type a full
path for common commands. There's IMHO no reason a normal desktop user
shouldn't be able to run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Wednesday 2007-12-19 at 17:35 -0800, Randall R Schulz wrote:
So am I, but I don't want to run apps as root.
Actually, that's not necessary. You can always become root for the
purpose of exercising privileged operations and then go back to be
On Wednesday 19 December 2007 16:42, Carlos E. R. wrote:
> The Wednesday 2007-12-19 at 16:29 -0800, Randall R Schulz wrote:
> >> Unfortunately, that's right. You need to be root to increase and
> >> even decrease I/O priority using program ionice.
> >
> > How odd. Thankfully, I'm Lord and Master of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Wednesday 2007-12-19 at 16:29 -0800, Randall R Schulz wrote:
Unfortunately, that's right. You need to be root to increase and even
decrease I/O priority using program ionice.
How odd. Thankfully, I'm Lord and Master of my machines!
So am I
On Wednesday 19 December 2007 15:47, Carlos E. R. wrote:
> The Wednesday 2007-12-19 at 15:23 -0800, Randall R Schulz wrote:
> >> Only if you are root.
> >
> > Is ionice different from (CPU) nice? I.e., is it not possible for
> > any user to lower the priority (increase the absolute nice value)
> >
Sloan wrote:
Gary Baribault wrote:
And just for your general information, with Beagle installed, SuSE was
using 1.5Gig of Memory and 256Meg of Swap.
After removing Beagle and a reboot, I have 887Meg free and no swap used,
I would think that Beagle qualifies as a HOG. I don't care what it
offers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Wednesday 2007-12-19 at 15:23 -0800, Randall R Schulz wrote:
Only if you are root.
Is ionice different from (CPU) nice? I.e., is it not possible for any
user to lower the priority (increase the absolute nice value) while
only root can improv
On Wednesday 19 December 2007 15:12, Carlos E. R. wrote:
> The Monday 2007-12-17 at 20:24 +0100, Anders Johansson wrote:
> > Fortunately there is a way of doing it - with ionice you can set IO
> > scheduling priority idle, and since it's the IO that kills you, it
> > should be good enough
>
> Only
On Mon, 2007-12-17 at 10:53 -0500, Aaron Kulkis wrote:
> Gary Baribault wrote:
> > Hi all,
> >
> > Anyone else seeing Beagle really kill performance? I have disabled
> > it and my machine finally is perky, but every now and then, I find it
> > in memory again. How do I arange it to chew up les
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Monday 2007-12-17 at 20:24 +0100, Anders Johansson wrote:
Fortunately there is a way of doing it - with ionice you can set IO scheduling
priority idle, and since it's the IO that kills you, it should be good enough
Only if you are root.
-
On Wed, 2007-12-19 at 13:59 -0800, Linda Walsh wrote:
> These days, an interactive desktop user should almost never
> have more swap than physical memory -- even having swap=memory
> is too slow in many cases if the swap is being used frequently
> (> once/week).
I have 2 GB of real memory and 10 G
Aaron Kulkis wrote:
Until they remove every trace of it from human existence,
except for snippets preserved for teaching purposes, under
the topic of "DO NOT DO THESE THINGS in a background services
programs"
---
Well it depends on your configuration, no doubt.
I saw one user with 512M m
Anders Johansson wrote:
Fortunately there is a way of doing it - with ionice you can set IO scheduling
priority idle, and since it's the IO that kills you, it should be good enough
---
I thought ionice only worked with the 'cfq' block scheduler.
Is that the suse default?
--
To unsubscrib
Gary Baribault wrote:
And just for your general information, with Beagle installed, SuSE was
using 1.5Gig of Memory and 256Meg of Swap.
After removing Beagle and a reboot, I have 887Meg free and no swap used,
I would think that Beagle qualifies as a HOG. I don't care what it
offers as an advanta
Dave Howorth wrote:
> Joe Sloan wrote:
>> in fact anything in /opt or /usr/local usually wasn't even in root's
>> path
>
> I should hope not! root should have a strictly limited path to limit
> security exploits.
I'm not sure the lack of finish characteristic of the old school unices
provides th
Joe Sloan wrote:
> in fact anything in /opt or /usr/local usually wasn't even in root's
> path
I should hope not! root should have a strictly limited path to limit
security exploits.
Cheers, Dave
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Aaron Kulkis wrote:
> Joe Sloan wrote:
>> I have to fix the path to deal with the complaints of users who complain
>> that e.g. "ifconfig" isn't installed, or who maybe have to type a full
>> path for common commands. There's IMHO no reason a normal desktop user
>> shouldn't be able to run many co
[EMAIL PROTECTED] wrote:
On Sunday 16 December 2007 05:56:05 pm Joe Sloan wrote:
David C. Rankin wrote:
rpm -e $(rpm -qa | grep beagle)
works nicely
It looks good, but it won't remove beagle because kerry needs it.
But in general I agree with your elegant approach.
Joe
You can safely remo
Kevin Dupuy wrote:
On Sun, 2007-12-16 at 21:46 -0600, Peter Van Lone wrote:
On Dec 16, 2007 4:39 PM, Joe Sloan <[EMAIL PROTECTED]> wrote:
The standard procedure for me on any new suse build is to nuke beagle
completely
Beagle doesn't give me any problems at all ... and I use it often to
"find
Joe Sloan wrote:
Gary Baribault wrote:
Hi all,
Anyone else seeing Beagle really kill performance? I have disabled
it and my machine finally is perky, but every now and then, I find it
in memory again. How do I arange it to chew up less memory and CPU or
kill it once and for all?
The stand
Joe Sloan wrote:
Peter Van Lone wrote:
On Dec 16, 2007 4:39 PM, Joe Sloan <[EMAIL PROTECTED]> wrote:
The standard procedure for me on any new suse build is to nuke beagle
completely
Beagle doesn't give me any problems at all ... and I use it often to
"find stuff" ... I guess if I was using th
Gary Baribault wrote:
Hi all,
Anyone else seeing Beagle really kill performance? I have disabled
it and my machine finally is perky, but every now and then, I find it
in memory again. How do I arange it to chew up less memory and CPU or
kill it once and for all?
You can't.
It's one of the
Linda Walsh wrote:
> No such thing in standard linux. The cpu nice doesn't affect
> the disk-io priority unless you have the non-standard "cfq" scheduling
> algorithm enabled. The default when I installed 10.2 recently, I believe
> was the 'anticipatory' deadline. Unfortunately, while it may
Rajko M. wrote:
On Sunday 16 December 2007 04:19:48 pm Linda Walsh wrote:
Gary Baribault wrote:
Hi all,
Anyone else seeing Beagle really kill performance? I have disabled
it and my machine finally is perky, but every now and then, I find it
in memory again. How do I arange it to chew up le
>
> Beagle-helper runs now with nice=19, so it is already the lowest priority
> and it will not make problem even on initial indexing. The beagled runs
> with nice=7, so it is also below most processes in the system.
>
> --
> Regards,
> Rajko
it will still eat up the ram and fill the swap space.
On Sunday 16 December 2007 04:19:48 pm Linda Walsh wrote:
> Gary Baribault wrote:
> > Hi all,
> >
> > Anyone else seeing Beagle really kill performance? I have disabled
> > it and my machine finally is perky, but every now and then, I find it
> > in memory again. How do I arange it to chew up l
On Mon, 2007-12-17 at 20:32 +0100, Anders Johansson wrote:
> On Monday 17 December 2007 19:58:18 JP Rosevear wrote:
> > Beagle already does nice itself and employ strategies for reducing work
> > when the CPU is not idle. However I/O is a problem and non-root
> > processes can't change their own
On Monday 17 December 2007 08:58:18 am JP Rosevear wrote:
> Beagle already does nice itself and employ strategies for reducing work
> when the CPU is not idle. However I/O is a problem and non-root
> processes can't change their own I/O priority iirc.
>
> -JP
> --
> JP Rosevear <[EMAIL PROTECTED
On Mon, 2007-12-17 at 09:18 -0500, JP Rosevear wrote:
> On Sun, 2007-12-16 at 16:41 -0500, Gary Baribault wrote:
> > Hi all,
> >
> > Anyone else seeing Beagle really kill performance? I have disabled
> > it and my machine finally is perky, but every now and then, I find it
> > in memory again.
On Monday 17 December 2007 13:24, Anders Johansson wrote:
> I think you're confusing "nice" with applications' getting priority when
> they're in the foreground (which is the windows strategy), but that's the
> other way around
Yes... I was alluding to the windoze strategy, but not confused abo
On Monday 17 December 2007 19:58:18 JP Rosevear wrote:
> Beagle already does nice itself and employ strategies for reducing work
> when the CPU is not idle. However I/O is a problem and non-root
> processes can't change their own I/O priority iirc.
Actually, they can. "All" they need is CAP_SYS_A
M Harris wrote:
> On Monday 17 December 2007 12:22, Sloan wrote:
>
>> It would be great if the beagle devs could take a page from
>> the boinc playbook, and only use CPU when it is not being used by other
>> apps.
>>
>You mean like the windoze devs...?
>
Nope, I mean the boinc devs -
On Monday 17 December 2007 13:44:20 M Harris wrote:
> On Monday 17 December 2007 12:22, Sloan wrote:
> > It would be great if the beagle devs could take a page from
> > the boinc playbook, and only use CPU when it is not being used by other
> > apps.
>
>You mean like the windoze devs...?
>
>
On Mon, 2007-12-17 at 06:44 -0600, M Harris wrote:
> On Monday 17 December 2007 12:22, Sloan wrote:
> > It would be great if the beagle devs could take a page from
> > the boinc playbook, and only use CPU when it is not being used by other
> > apps.
>You mean like the windoze devs...?
>
>
On Monday 17 December 2007 12:22, Sloan wrote:
> It would be great if the beagle devs could take a page from
> the boinc playbook, and only use CPU when it is not being used by other
> apps.
You mean like the windoze devs...?
cpu timeslice should *never* be in the hands of app developers. Th
Gary Baribault wrote:
> And just for your general information, with Beagle installed, SuSE was
> using 1.5Gig of Memory and 256Meg of Swap.
>
> After removing Beagle and a reboot, I have 887Meg free and no swap used,
> I would think that Beagle qualifies as a HOG. I don't care what it
> offers as a
On Mon, 2007-12-17 at 11:38 -0500, Gary Baribault wrote:
> And just for your general information, with Beagle installed, SuSE was
> using 1.5Gig of Memory and 256Meg of Swap.
>
> After removing Beagle and a reboot, I have 887Meg free and no swap used,
> I would think that Beagle qualifies as a HO
And just for your general information, with Beagle installed, SuSE was
using 1.5Gig of Memory and 256Meg of Swap.
After removing Beagle and a reboot, I have 887Meg free and no swap used,
I would think that Beagle qualifies as a HOG. I don't care what it
offers as an advantage, it isn't worth that
Kevin Dupuy wrote:
Some people have a lot of trouble with Beagle, I don't. If you want to
kill it off for good, you can uninstall it. What are your computer's
specs, I'm trying to figure out why some are having issues and others
aren't.
I don't seem to have a problem with it.
Oh. I'm thinki
On Mon 17 December 07 07:39, Gary Baribault wrote:
> Well, it's not quite that easy... Beagle libraries are used by a bunch
> of installed programs, but I un-installed all of the rest and have my
> nice snappy thunderbird back .. :-)
>
> Thanks for all of the suggestions, made for fun reading
>
>
On Sun, 2007-12-16 at 16:41 -0500, Gary Baribault wrote:
> Hi all,
>
> Anyone else seeing Beagle really kill performance? I have disabled
> it and my machine finally is perky, but every now and then, I find it
> in memory again. How do I arange it to chew up less memory and CPU or
> kill it o
Well, it's not quite that easy... Beagle libraries are used by a bunch
of installed programs, but I un-installed all of the rest and have my
nice snappy thunderbird back .. :-)
Thanks for all of the suggestions, made for fun reading
Gary B
Joe Sloan wrote:
> [EMAIL PROTECTED] wrote:
>
>> On
[EMAIL PROTECTED] wrote:
> On Sunday 16 December 2007 05:56:05 pm Joe Sloan wrote:
>> David C. Rankin wrote:
>>> rpm -e $(rpm -qa | grep beagle)
>>>
>>> works nicely
>> It looks good, but it won't remove beagle because kerry needs it.
>>
>> But in general I agree with your elegant approach.
>>
>> J
1 - 100 of 114 matches
Mail list logo
