On Mon, 2009-11-23 at 13:32 -0800, John Andersen wrote:
On Monday 23 November 2009 02:31:57 am David C. Rankin wrote:
Guys Keep an eye on beagled. Tonight after cron daily, beagled hung with the processor stuck at 43%. I thought it was just indexing, so I let it run. Then 4 hours later it was still stuck at 43% and had consumed a bit over 500M of RAM in the process. I don't know the exact cause or any more of the symptoms. This is the first time I have seen it. Anybody else had to shoot the dog lately? I suppose in your line of work full text searches are pretty important, but for my use I've found "locate" to be all I need. I was migrating from 10.3, to 11.2 via a clean install. While backing up the hard disks I was preparing to wipe, I was astounded at the sheer overall size and number of files in user's .beagle directories on the old system. What an incredibly horrible design.
So, you want to index content without creating indexes?
No wonder it could grind a machine to dust.
It has an imperceptible effect on system performance. My .beagle directory is 137MB. The files are Lucene indexes which are very fast. The same indexing strategy is used in numerous 'enterprise' search appliances. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org