> I've submitted a bug in debian covering beagle not indexing thunderbird mail
> that is located in a non-standard location.
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=407242
>
> A follow up bug was posted to the gnome bugzilla
> http://bugzilla.gnome.org/show_bug.cgi?id=397789
Something r
All,
I've submitted a bug in debian covering beagle not indexing thunderbird mail
that is located in a non-standard location.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=407242
A follow up bug was posted to the gnome bugzilla
http://bugzilla.gnome.org/show_bug.cgi?id=397789
Basically I keep
D Bera wrote:
>> Once again this document was written to give some input to the future
>> development to get better ones :-)
>
> Thanks Michal for your excellent document (and experiments). The
> results will definitely be helpful in creating a better beagle.
>
> Btw, as requested in the tracker
Michael Biebl wrote:
> 2007/1/17, jos poortvliet <[EMAIL PROTECTED]>:
>> Op woensdag 17 januari 2007, schreef Jamie McCracken:
>> > Im not so sure - the problem is on some machines using a sustained 100%
>> > cpu can cause laptops to heat up quickly, become more noisy (fans),
>> > drain battery lif
> Once again this document was written to give some input to the future
> development to get better ones :-)
Thanks Michal for your excellent document (and experiments). The
results will definitely be helpful in creating a better beagle.
Btw, as requested in the tracker mailing list
(http://mail
Hi,
I just checked out the latest version from svn and installed new mono
packages from debian.meebay.net (version 1.2.2 i believe) because beagle
complained about 1.1.17 being too old.
Now compiling worked just fine but running the resulting beagled dies
like this:
** (/usr/local/lib/beagle/Beag
Joe Shaw wrote:
>
> Sadly, they are using Beagle 0.2.7 in their tests, a 7 month old
> version. :( In releases since then, we added support for wildcard
> searches, indexing of archives and their contents, and of course tons of
> memory use fixes. The doc was originally written in November and
>
Hi,
On Wed, 2007-01-17 at 16:57 -0500, D Bera wrote:
> Michal Pryc and Steven Xusheng Hou of Sun compared the four popular
> desktop indexing systems - JIndex, Tracker, Strigi and Beagle.
> http://mail.gnome.org/archives/tracker-list/2007-January/pdfLkb0uuBAEw.pdf
>
> Its a nice comparison, inc
Hi all,
Michal Pryc and Steven Xusheng Hou of Sun compared the four popular
desktop indexing systems - JIndex, Tracker, Strigi and Beagle.
http://mail.gnome.org/archives/tracker-list/2007-January/pdfLkb0uuBAEw.pdf
Its a nice comparison, including stats and charts. You might find it
interesting i
On Wed, 2007-01-17 at 14:13 -0500, Joe Shaw wrote:
> If you have the time/cycles to spare, you
> could just move your ~/.beagle directory out of the way and have it
> reindex from the start, and move it back afterward.
Indeed. Figured that is what I will do if beagled continues to run with
reason
Hi,
On Wed, 2007-01-17 at 14:08 -0500, Brian J. Murrell wrote:
> Memory usage: VmSize=101.5 MB, VmRSS=41.2 MB, GC.GetTotalMemory=13164544
The RSS is fairly reasonable there, but the 13 megs for
GC.GetTotalMemory is a little high. I suspect that is caused by the
memory-unfriendly caching we were
On Wed, 2007-01-17 at 11:06 -0500, Joe Shaw wrote:
> Hi,
Hi All,
> Just FYI, VmSize is largely irrelevant; it's not an indicator of how
> much memory an application is using. RSS and GC.GetTotalMemory are the
> two interesting statistics printed by --debug-memory.
>
Well, heap-shot crashed aga
Hi,
On Wed, 2007-01-17 at 16:35 +, Stringer Leon (West Midlands
Ambulance Service NHS Trust) wrote:
> It reports: Dl+
This means that it's in disk wait; for some reason it's waiting on IO,
presumably to/from the Samba server.
> "" tid=0x0xb7f1e6d0 this=0x0x21e40:
> at (wrapper managed-to-n
Thanks for continuing to look at this.
>From: Joe Shaw <[EMAIL PROTECTED]>
>Run it on the samba share again, and when it seems to block, do a "ps
>ax" to see if the process is stuck in the D state, or otherwise just
>stopped (probably the S state, or perhaps R).
It reports: Dl+
>Also, running
Hi,
On Wed, 2007-01-17 at 09:30 -0500, Brian J. Murrell wrote:
> On Wed, 2007-01-17 at 09:10 -0500, D Bera wrote:
> > > Well, in fact beagled only grew from 87MB to 94MB before this bug
> > > struck. Very reasonable growth IMHO.
> >
> > Thats VMSize - right ? Then its reasonable.
>
> Yes, very
Hi,
On Wed, 2007-01-17 at 13:13 +, Stringer Leon (West Midlands
Ambulance Service NHS Trust) wrote:
> Another thing I noticed in this test is that when I tried the sandbox
> test, I could stop beagled with Ctrl+C, and it would stop cleanly.
> However, when I try "beagled --fg --debug" I have t
> In the case of the last (and indeed, this current) run though, it would
> probably just show a very reasonable and completely understandable
> situation, no?
I hope it does.
> > You might delete the older ones - since you started the new run with
> > better (read: worse for your computer) perfo
On Wed, 2007-01-17 at 09:47 -0500, D Bera wrote:
>
> You do not need to wait for the full run. If its grown to, say, 200
> MB,
No, of course not. Each snapshot is interesting in itself.
But I have not grown to 200MB yet. Still holding steady at 101.5MB.
> you can stop it. A few snapshots (e.g
> Indeed. I have restarted beagled with heap-shot and am currently at a
> VmSize of 100MB.
You do not need to wait for the full run. If its grown to, say, 200
MB, you can stop it. A few snapshots (e.g. every tenth one, basically
first, last and a 10 in the middle) would be helpful to know what is
On Wed, 2007-01-17 at 09:10 -0500, D Bera wrote:
> > Well, in fact beagled only grew from 87MB to 94MB before this bug
> > struck. Very reasonable growth IMHO.
>
> Thats VMSize - right ? Then its reasonable.
Yes, very reasonable I think.
> The snapshots from your earlier run would have been bet
> Well, in fact beagled only grew from 87MB to 94MB before this bug
> struck. Very reasonable growth IMHO.
Thats VMSize - right ? Then its reasonable.
> Do you still think there is something meaningful in the snapshots? I do
> have 99 of them.
The snapshots from your earlier run would have bee
On Tue, 2007-01-16 at 22:24 -0500, Joe Shaw wrote:
> Hi,
Hi,
> I've seen this on occasion, it's a bug in heap-shot.
:-(
> In any case, you
> should have some workable snapshots there.
Well, in fact beagled only grew from 87MB to 94MB before this bug
struck. Very reasonable growth IMHO.
Do yo
>From: "D Bera" <[EMAIL PROTECTED]>
>> However, if I try a search the GUI window reports "Search service not
>> running", and no "Parsed query" message is shown.
>
>You need to set BEAGLE_HOME for beagle-search too i.e. start
>beagle-search from the command line as $ BEAGLE_HOME=/tmp/sandbox
>be
23 matches
Mail list logo
