search for: auto_flush

...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) and I have an after_save filter in my model as follows: def update_index INDEX << self.to_doc end Is there anything I can do to improve this performance? Thanks, Tom

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

...he console, I try this: >> index = Article.ferret_index => #<Ferret::Index::Index:0x2b686dc76860 @writer=nil, @default_input_field=:id, @qp=nil, @dir=#<Ferret::Store::FSDirectory:0x2b686dc76748>, @mon_entering_queue=[], @default_field=["title"], @key=:id, @mon_count=0, @auto_flush=true, @open=true, @close_dir=true, @id_field=:id, @mon_owner=nil, @reader=nil, @searcher=nil, @options={:lock_retry_time=>2, :path=>"script/../config/../config/../index/development/article", :create_if_missing=>true, :default_field=>["title"], :analyzer=>#<Ferr...

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

...ave 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 something I''m doing wrong? FYI, I''m doing my development on Windows. Thanks, Carl class Resume < ActiveRecord::Base include Ferret has_and_belongs_to_many :users @@index = Index::Index.new(...

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 directory and throws this exception: /usr/local/lib/ruby/gems/1.8/gems/ferret-0.3.2/lib/ferret/store/fs_...

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 of memory. I am on ferret 0.9.3 with C extentions. Ubuntu Linux is the OS. -- Posted via http://www.ruby-forum.com/.

...port/buffered_logger.rb:96:in `synchronize'' from /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.2/ lib/active_support/buffered_logger.rb:96:in `flush'' from /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.2/ lib/active_support/buffered_logger.rb:116:in `auto_flush'' This doesn''t seem right as my daemon is reusing code that makes calls to Rails.logger. Am I missing something? thx.

...>#<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"=>...

...>#<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"=>...

...ngth = 50 from /usr/lib/ruby/gems/1.8/gems/ferret-0.10.0/lib/ferret/index.rb:204:in `<<'' from /usr/lib/ruby/1.8/monitor.rb:229:in `synchronize'' from /usr/lib/ruby/gems/1.8/gems/ferret-0.10.0/lib/ferret/index.rb:186:in `<<'' (...) When I tried with auto_flush, it''s worst :( Any ideas ? -- Posted via http://www.ruby-forum.com/.

...uld be to use a IndexReader afaik. I would suggest to do it that way: index = Ferret::Index::Index.new( :path => ''/some/path'', :readonly => true ) i guess this is far easier than using the Ferret::Index::IndexReader. Other parameters like auto_flush can be ignored. Furthermore, reading several indexes should be done like that: index = Ferret::Index::Index.new( :path => [ ''/some/path'',''/another/path'' ], :readonly => true ) so you dont need to play around with MultiSe...

...As well as working on the performance, the locking system has had a few changes to prevent some of the problems it has been causing people. Now, if you cancel a process while it has a lock open, the lock should still be released. Also, you can set the index to auto flush; index = Index::Index.new(:auto_flush => true) This will make sure no locks are kept open after updating the index. You won''t need to call flush anymore. This is very useful if you have multiple processes modifying the index as you might have in a Rails application. Also, it should now compile with the MSVC compiler on wi...

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

...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 sure how to do this. As I understand it I have to do this for the Index class and not for the model that acts_as_ferret, right? How exactly do I do this? Do I just have to make a new Index model? I hope someone can help me out. -- Jeroen Janssen

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

...0xb77dc1f4 @options={:default_field=>:*, :dir=>#<Ferret::Store::RAMDirectory:0xb77dc1b8>, :analyzer=>#<Ferret::Analysis::StandardAnalyzer:0xb77dc0c8>, :lock_retry_time=>2}, @mon_entering_queue=[], @qp=nil, @searcher=nil, @mon_count=0, @default_field=:*, @close_dir=true, @auto_flush=false, @open=true, @mon_owner=nil, @id_field=:id, @reader=nil, @mon_waiting_queue=[], @writer=nil, @default_input_field=:id, @dir=#<Ferret::Store::RAMDirectory:0xb77dc1b8>> *** Now let''s add 3 strings to the index *** irb(main):005:0> ["While you were out pet care&quo...