| 1 |
On Tue, 2007-02-27 at 14:21 +0100, Kristian Poul Herkild wrote: |
| 2 |
|
| 3 |
> Beagle is not supposed to use an awful lot of CPU-time, except for rare |
| 4 |
> peaks. If it uses a lot of CPU-cycles for more than a few seconds it's a |
| 5 |
> bug - most likely in a plug-in. Especially the SVG plug-in tends to have |
| 6 |
> issues. |
| 7 |
|
| 8 |
Well it started to get really annoying when I added my |
| 9 |
ebook/documentation directory to the scanned dirs (it's an nfs share |
| 10 |
with PDFs), that made the beagled-helper thingy go berzerk on my poor |
| 11 |
old processor. Maybe that is an nfs thing, or the PDFs were nasty. |
| 12 |
Having it scan just my home dir was OK most of the time, I admit. But |
| 13 |
the Documentation/Ebook indexing was pretty much the only reason I was |
| 14 |
looking into beagle in the first place ;) |
| 15 |
|
| 16 |
> The memory consumption is however quite high. |
| 17 |
|
| 18 |
Yeah that was another thing bugging me, having some merge running in the |
| 19 |
background and beagle kicking in made this thing crawl :( |
| 20 |
|
| 21 |
|
| 22 |
Jürgen |
| 23 |
-- |
| 24 |
ICQ #81510866 - http://the-gay-bar.com - MSN tante@×××××××××.de |
| 25 |
Occam's Razor: |
| 26 |
-"Entia non sunt multiplicanda praeter necessitatem."- |
Archives