Mailinglist Archive: opensuse-gnome (127 mails)

[James Tremblay <jamesat@xxxxxxxxxxx>]

On Wed, 2007-08-22 at 08:34 -0400, Joe Shaw wrote:
> Hi,
> 
> On 8/22/07, Karl Eichwalder <ke@xxxxxxx> wrote:
> > Patrick Shanahan <ptilopteri@xxxxxxxxx> writes:
> >
> > > Don't see that on my 10.1 openSUSE.  Don't see any problems w/beagle
> > > at all.
> >
> > Maybe, the problems are caused by different network environments, just
> > guessing.
> 
> Possibly.  Beagle does some extra work for remote (NFS, SMB) home
> directories such that the index is built locally (in /tmp) and
> checkpointed back to home every now and then.  But that would mostly
> IO-bound (specifically network) and not CPU-bound.
> 
> Other than that, network configuration shouldn't matter.
> 
> > Or there are strange interactions with our build system or my
> > way of Web browsing.
> 
> Certainly creating tons and tons of files means that the indexer has
> to do more work, but if the build system doesn't build in your home
> directory, then this shouldn't be an issue.  (I guess it wouldn't be
> for autobuild or the OBS.)
> 
> Web browsing may have caused an impact a while ago (more than a year
> at this point) but shouldn't matter now.  I guess if your browser
> continuously updates a file in your home directory by writing to it
> and closing and reopening the file, this would cause problems -- we
> have seen this with some BitTorrent cllients, but never browsers.
> 
> On 8/22/07, Karl Eichwalder <ke@xxxxxxx> wrote:
> > Since quite some time, beagled-helper now eat ~99% of one (virtual) CPU
> > and the fans are spinning up...  ATM, I see:
> >
> > Scheduler:
> > Count: 278
> > Status: Executing task
> > Delayed 0 (8/22/2007 1:45:38 PM)
> > Crawling /suse/ke/News/cache/nnimap+suse:INBOX.cestina
> >
> > Pending Tasks:
> > 1 Immediate 0 (8/22/2007 1:48:09 PM)
> > http://skillingstad.no/packages/
> 
> The question here really is: does this change over time, say, 5 minutes?
> 
> If not, you've found a bug; sending SIGUSR2 to the beagled-helper
> process will cause beagle to log to its
> ~/.beagle/Log/current-IndexHelper file which file it's working on.
> With that information, you can run the beagle-extract-content tool on
> that file and see if it too hangs.  Then I just need to debug *why*
> that behavior happens for that specific file.
> 
> Thanks,
> Joe

START A NEW THREAD!!!!!
-- 
James Tremblay
Director of Technology
Newmarket School District
Newmarket,NH
http://en.opensuse.org/Education
"let's make a difference"

-- 
To unsubscribe, e-mail: opensuse-gnome+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-gnome+help@xxxxxxxxxxxx