search for: liivid

Hi all, there was a recent thread[1] on rails-deploy about Ferret in which a lot of people complained of problems using it in production. I''ve been using Ferret (with DRb) for many months now with no serious issues. I''m assuming the posters know what they''re doing so I''m guessing they''re just using Ferret in higher-scale environments than me. I

...return end @rebuilding = true The big problem was in new_index_for, which always uses the same path, and causes the multiple rebuilds to be stomping on each other. It''s not necessary to fix this after adding the above though. Thanks again. -- Alex Neth Liivid Inc / cribQ www.liivid.com / www.cribq.com On Jan 28, 2008, at 3:45 PM, ferret-talk-request at rubyforge.org wrote: > Date: Sat, 26 Jan 2008 10:53:22 +0100 > From: Jens Kraemer <jk at jkraemer.net> > Subject: Re: [Ferret-talk] ferret success stories? > To: ferret-talk at rubyfo...

> From: Jens Kraemer <jk at jkraemer.net> > Subject: Re: [Ferret-talk] Performance before and after optimization > On Sat, Nov 03, 2007 at 08:49:17PM +0800, Alex Neth wrote: > [..] >> 2) Can I keep a second index so that it doesn''t get locked during >> optimization and then switch to the optimized index? Perhaps the >> index >> is not really

...rra.com> > Subject: Re: [Ferret-talk] Ferret-talk Digest, Vol 25, Issue 2 > To: ferret-talk at rubyforge.org > Message-ID: > <314ee0450711071401l97b4be8j5e298d7d24383ea3 at mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On 11/7/07, Alex Neth <alex at liivid.com> wrote: >> Thanks Jens. Any suggestion on how to get a two index solution >> working with acts_as_ferret? > > I rolled my own with methods in my model class, something like this: > > def self.setup_new_index(location) > config = aaf_configuration[:ferre...

As of some recent version of Postgres, plpgsql is created for new databases by default, but the sql schema export (config.active_record.schema_format = :sql) expots a create command in development_structure.sql, resulting in an error. CREATE PROCEDURAL LANGUAGE plpgsql; I could not find the version this changed in, however it is noted here:

I have had to fix a few issues with AAF in order to get it working well for myself in a production environment. I''m using the latest "release" version which is 0.4.1: 1) When there is no index in place, every request starts a new rebuild. While there is some code in place to allow this to happen during testing, personally I see no reason to even test for this,

I have an index with a few hundred thousand records. The index is generally very fast, with sub 100ms responses. However if I start adding records, it gets extremely slow, up to over 2 seconds per query. This is true even if I am not currently indexing until I optimize the index. In order to work around this, I index in bulk and immediately optimize. This is not ideal for the