Re: Gnome Journal Article and General Beagle Publicity


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:
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

Debajyoti Bera @
beagle / KDE fan
Mandriva / Inspiron-1100 user

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]