Re: Gnome Journal Article and General Beagle Publicity

[Kevin Kubasik <kevin kubasik net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

While I love the enthusiasm, beagle still is a little to raw for me to
think were at _that_ level of 100% plug and play. Personally, I think
were getting closer, but there is still a lot of work before the dev
team would put such a stamp on it. But there is also a major difference
between a distro saying an application works and the dev team. Its great
that under forsight, beagle has minimal issues, but there are thousands
of possible configurations out there, and success on one set of them
does not mean all cases.

That being said, I'm really psyched that it works with such success on
forsight!

As to the 0.3 question, theres  nothing at the moment, so this is
probably a 'wait-for-joe-to-weigh-in' type thing. But if I were to
guess, the showstoppers would be:
- - Unified Indexies
- - SoC Merges
- - Timestamp cleanup in API
With other memory reductions and stability issues also obviously being
fixed. But wait for Joe before taking anything I said to heart ;)

Cheers,
Kevin Kubasik
- -

Ken VanDine wrote:
> I do think it is ready for plug and play.  In Foresight, we have it
> setup to run automatically.  The user doesn't have to do anything.  We
> do also keep it very current, we always get new versions cooked up the
> same day beagle releases.  It has really worked pretty well for most
> people for some time now.  Most folks don't even understand beagle.
> They just know they pop open that search tool or type in some text in
> the deskbar applet and it does the right thing.  The user doesn't really
> know it is beagle doing the work.  They have have a great search tool.
> That is the way it should be, imho.
> 
> --Ken
> 
> On Sun, 2006-11-12 at 20:59 -0500, D Bera wrote:
>> Hi
>>
>>> beagle in Foresight for well over a year now.  The great news is for
>>>> quite a while now there haven't been any users asking "What is this
>>>> beagled thing and why does it use all my memory?".
>> Only if you dont do the rounds of distro bugzilla and newbie forums.
>> Those places are full of beagle eating CPU and memory problems (some
>> of them are due to some old buggy version of beagle that hasnt been
>> updated in the distros). I dont think beagle is newbie ready i.e.
>> plug-and-play yet.
>>
>>> Especially with the most recent release, and the upcoming changes, which
>>> is why I think its worth talking about. Using some of the practice
>>> mentioned here:
>>> http://beagle-project.org/Thunderbird
>>> I run beagle (with the thunderbird backend and about 10.000 mails) at
>>> about 45 MB resident for the master process and
>>> Debug: Helper Size: VmRSS=34.2 MB, size=3.55, 63.7
>>> its not perfect, but its certainly far more passive then before, and
>>> without the tbird backend, its significantly better.
>> Kevin, I had a brief glance at the thunderbird backend. I didnt see
>> any obvious place which takes a lot of memory. If the concern is the
>> ReadToEnd() in the mork parser, then you can try to replace the huge
>> content string with a StreamAsArray type implementation. I replaced
>> one ReadToEnd() in the html filter in a similar way, check
>> Filters/HtmlAgilityPack/HtmlDocument.cs - it contains the
>> implementation. Might be useful.
>>
>> - dBera
>>
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iQIVAwUBRVgRLf3xZFNDM330AQi0FQ/+Mgwi4gNHgKkqzrFTy0IZPVeU9se2Kf5u
1HXmzBff4RVucCPzzXRwZXmw7Jk2qttdhRXAwWqziPdTtMYBwIrD1NeSwRdt25ZA
PT7Nlaw9kSscNVCp0ueKFLnHI2M75G7bSJEXO9D/jY/9kN7YxU8QOYEHXtjyHg/8
r2ip5AccTYDw2HOgv0ljEdpD63ZZB6lENEs4Vm2zSWa9eKQcanAYVyU1hWkpqSVA
Fow+I11RPrXzZO/2fXxWeQgTKD9lk1oY71X7lhM92EqwL1bh7nXZ14hMBS/5UQhj
yKVMkWH0SVUkd6axxoXG4czFsNttGo/BfaR5Tbdd6vyVsf5DZuO5QX6Yxmn5j88s
nFZovtqbNkuT15H21j/e2qoeo2j5VkSkJCWYcWqBXVNitvjACNOSkKLc1zSJ1JxR
8HQNTfcwVHCCfOg77vYrVr2A8TsFv6Hh+KiYR8HmYwKFLCDGC+8vml9VstTm2N2E
jCFsy5WiXf50Rid59zjXv+8HRPXRHV6RDhStoYKceNR9W7T5cUqqdS9U8QkD9h0C
Cmh7ZYiTct8kI7Fqe2fMHy0uO16hqnpW1UoySF+xQF7gPJ+rQCI/oT3sw/JeqLZn
qmiFEz2QfIGI72AxxQyLHLUVU1NCaQQbQSs7VDOL4y4W+hMXkC/E5khDoEcaLEcV
BDyrjHDjFMo=
=FG7t
-----END PGP SIGNATURE-----