search for: auto_flushing

Hi, I am experiencing very poor performance when updating my index. For example, to update the index for 10 documents, it is taking 3 to 4 seconds. My index is currently very small... with probably less than 100 docs in it. I have created my index as follows: GIFT_INDEX = Index::Index.new(:path => "#{index_dir}/gift", :key => ''id'', :auto_flush => true)

Hi - I upgraded to Ferret 0.11.3 from 0.10.13. I used to index 10,000 records in 10 secs. Now it takes 13 minutes. (That''s a factor of ~75x) Did something change in the flush semantics, or something? Thanks! Schnitz -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I have been using Ferret on ruby-forum.com for a few days. While the searching works with reasonable performance, there are a lot of problems related to indexing. Sometimes the process hangs with 100% CPU usage, sometimes it leaves Lockfiles in the directory (causing other processes to fail while one ist still working), sometimes it even crashes with a segfault. I''m going to

Hi folks, I''ve working and playing with acts_as_ferret and follow this fantastic tutorial: http://www.railsenvy.com/2007/2/19/acts-as-ferret-tutorial When I try to implement the field storage tip, it crash. So, I try to make it via script/console: 1. I have a simple model called Articles: class Article < ActiveRecord::Base acts_as_ferret :fields =>

Is anyone using ferret with Mongrel/Mongrel-cluster? The first one or two times I access the ferret index it works fine, but then it throws a write lock error StandardError (: Error occured at <index_rw.c>:703 Error: exception 6 not handled: Could not obtain write lock when trying to write index ): I need to do more testing on this to narrow down the problem/solution but just wanted to

I have a model class in rails that has a class variable that is a ferret index. For some reason, the methods in my class that refer to the class variable are getting lock conflicts. Can anybody see any obvious reason why? I notice that it keeps leaving a lock file in the index directory. I thought auto_flush was supposed to remove the lock automatically after every operation. Is there

I am getting this issue also... Does anyone know what this is? When will Acts as Ferret be available for v10? Thanks for your help in desperation! Caspar wrote: > Okay previous post related to me trying to fix this problem with an > upgrade to ferret 0.10.0 but acts as ferret is obviously not compatible > with this new version of ferret. > My app is about to go into production and

Hi, I have ferret working fine on my Dev machine using a relative index path as follows: USER_INDEX = Index::Index.new(:path => "indexes/user", :key => ''id'', :auto_flush => true) And the indexes/user directory is located directly off the root of my project tree. But when I migrate this same code to my shared TextDrive account, Ferret cannot find the index

I am a bit puzzled. I am having issues with memory leaking away. It seems to be related to searching documents by ''id'' column value. This is what I am doing: cached_annotations = Ferret::Index::Index.new(:path => "#{RAILS_ROOT}/db/ferret/tmp/annotations", :auto_flush => false) 100000.times { |x| doc=cached_annotations[x.to_s] } Every 100000.times eats 100MB

I am trying to leverage the daemons gem but I am confused about the proper way to set up logging. I am able pass options which configure stdout to go to a log file but it seems like all calls to Rails.logger are disabled as I see the following message in my output: usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/ active_support/buffered_logger.rb:99:in `write'': closed

...>#<struct ActiveRecord::ConnectionAdapters::ColumnDefinition base=#<ActiveRecord::ConnectionAdapters::MysqlAdapter:0xb6fc6f50 @logger=#<ActiveSupport::BufferedLogger:0xb70935f0 @log=#<File:/home/grant/stuff/ruby/rails/auction-demo-mysql/log/development.log>, @no_block=false, @auto_flushing=1, @buffer=[], @level=0>, @runtime=0.134179830551147, @quoted_column_names={"unique_schema_migrations"=>"`unique_schema_migrations`", "schema_migrations"=>"`schema_migrations`", "id"=>"`id`", "auctions"=>&qu...

...>#<struct ActiveRecord::ConnectionAdapters::ColumnDefinition base=#<ActiveRecord::ConnectionAdapters::MysqlAdapter:0xb6fc6f50 @logger=#<ActiveSupport::BufferedLogger:0xb70935f0 @log=#<File:/home/grant/stuff/ruby/rails/auction-demo-mysql/log/development.log>, @no_block=false, @auto_flushing=1, @buffer=[], @level=0>, @runtime=0.134179830551147, @quoted_column_names={"unique_schema_migrations"=>"`unique_schema_migrations`", "schema_migrations"=>"`schema_migrations`", "id"=>"`id`", "auctions"=>&qu...

In a rails script (something in the "script" dir with the good require) I added many document (around 4000) to an index globaly instanciate (and build if not present) in config/environment.rb. I ran 3 three times my script (I deleted my index every time before), and only the third was successful. That was STRANGE ! :) These are the errors :

Hey .. I was thinking about the way I need to use the Ferret::Index::Index Class and its subclasses .. i find it somehow complex .. I think this can be done more easily .. Most of the Time a user needs to open up a index to do queries, the best way would be to use a IndexReader afaik. I would suggest to do it that way: index = Ferret::Index::Index.new( :path =>

Hi folks, This latest release of Ferret has a lot of improvements. There have been substantial improvements to performance. Try it for yourself to see. I won''t be publishing any numbers just yet. I will say though that it''s still about 2-4 times slower than Lucene with the extension installed. There is also some performance improvements in the pure Ruby version if you

Hi all This week I have worked with Rails and Ferret to test Ferrets (and Lucenes) capabilities. I decided to make a mixin for ActiveRecord as it seemed the simplest possible solution and I ended up making this into a plugin. For more info on Ferret see: http://ferret.davebalmain.com/trac/ The plugin is functional but could easily be refined. Anyway I want to share it with you. Regard it as a

Hi all This week I have worked with Rails and Ferret to test Ferrets (and Lucenes) capabilities. I decided to make a mixin for ActiveRecord as it seemed the simplest possible solution and I ended up making this into a plugin. For more info on Ferret see: http://ferret.davebalmain.com/trac/ The plugin is functional but could easily be refined. Anyway I want to share it with you. Regard it as a

Hi, I''m using acts_as_ferret in with a mongrel and I'' m getting locking errors that after a while result in a corrupt database. I know about the problem with different processes writing to the index but I haven''t been able to get the DRB server working properly yet. I read on this list that another solution is to set :auto_flush to true but I''m not

I am having some great trouble keeping my Ferret indexer for ActiveRecord working. First the get_field_names disappears (now back), then I am collectig some major trouble with locking. Same thing here: exception 6 not handled: Could not obtain write lock when trying to write index A snippet like this just deadlocks retrying endlessly: begin @ferret_index << doc

I was having some odd results when working with acts_as_ferret (current trunk), so I decided to test with the current version of ferret to see if I encountered the same problem. I did. Here are the details: installed ferret 0.10.10 on debian sarge with ''sudo gem install ferret'' (btw, same results on OSX) opened up an irb session: irb(main):001:0> require