similar to: ferret performance before optimization

hello, I am actually indexing thousands of 1ko text documents using ferret and acts_as_ferret, and i face performance problems. I takes me hours to index 20 000 1ko text documents. Methology used : I create and object, fulfill it with the text, and save it. So it is automaticly indexed. Is there a way to make it faster ? ( remove the auto optimize option somewhere ?) Thank you if you have any

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

Hello Jens, Will bulk_index be available in ferret 0.11.5 ? -- Posted via http://www.ruby-forum.com/.

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

If I disable ferret in my environment file and then run a cron job every hour to index the records that have been added/changed, do I enable Ferret just in the script that does the hourly indexing? Or do I somehow need to tell the process that runs the Ferret DRB server that it should start writing to the index again? Thanks in advance. Erik

Hey all, After dabbling with ActiveSearch, we''re coming back around to take another look at Ferret. ActiveSearch slowed to a crawl after indexing about 20k documents, each 20 lines each. This time we may attempt to create multiple Ferret indexes (isolating each organization''s data individually), since we eventually could have upwards of 20k documents for some

Hi, We''re happily using Ferret through acts_as_ferret on a Rails website, but we have an issue with rebuilding indexes. The Rails project directories are on an NFS mounted volume and running Model.rebuld_index there seems to take 60-100 times longer than it does on a local filesystem (e.g. /tmp). What we''d like to do is rebuild our indexes in say /tmp, then copy them back when

We are using Ferret on our site answeru.com. Today all of a sudden we started getting Ferret errors while users were trying to register or log into the system. I am not a Ferret techie - I apologize if a similar problem has already been asked or if it is not really a Ferret issue. Any ideas: IO Error occured at <except.c>:79 in xraise Error occured in fs_store.c:324 - fs_open_input

Hello list, I just started using ferret and it really doesn''t go my way. Doing gem install ferret outputs -> make install /usr/bin/install -c -m 0755 ferret_ext.so /var/lib/gems/1.8/gems/ ferret-0.10.13/lib make clean Successfully installed ferret-0.10.13 Installing ri documentation for ferret-0.10.13... Installing RDoc documentation for ferret-0.10.13... In ferret.rb ->

Dave and all, I run a medium RoR app using Ferret and acts_as_ferret. I get a lot of lock errors. Not always but around 5% of all searches (aspecially during peak periods). Here are the messages I get: A NameError occurred in szukaj#index: uninitialized constant Ferret::Index::Index::LockError [RAILS_ROOT]/vendor/rails/activesupport/lib/active_support/dependencies.rb:478:in

Using the current ferret gem (on Win-XP): irb(main):001:0> require ''ferret'' c:/ruby/lib/ruby/1.8/fileutils.rb:950: warning: already initialized constant OPT_TABLE => true irb(main):002:0> include Ferret => Object irb(main):003:0> index = Index::Index.new => #<Ferret::Index::Index:0x3477ba8 @qp=nil, ...> irb(main):004:0> index << "This is

I need to reset the ferret index between test runs. It seems like there are a few ways to reset the ferret index. * Deleting the index directory -- is this really bad form? * calling rebuild_index * (any others?) What would y''all recommend? (Sorry, I''m from Texas) Preferably, I''d like a way to reset the index that I can integrate into a selenium test. -David

QueryParser fails badly allocating enormous amount of memory when processing query strings with special/accented characters. See: irb(main):002:0> require ''rubygems'' irb(main):003:0> require ''ferret'' irb(main):004:0> include Ferret irb(main):005:0> index = Index::Index.new irb(main):008:0> index << "something" # Now the error

Greetings. Apologies if I missed something like this in the archives or internet, but I''m having issues using Ferret with Rails. Specifically, I have a class class "Weight" in my application (it happens to be a model). My app runs perfectly fine until it first executes "require ''ferret''". At that point, my definition of the class "Weight"

Hi guys! Been reading this list for a while. I have two repeatable Ferret crash bugs, both seg faults. 1. The first bug appears to seg fault Ferret when you use quotes in a search argument (eg ''file_name:"file name"'') 2. The second bug appears to seg fault Ferret when you attempt to index text with very long tokens (above 256 chars). It may have something to do with

Hello. I''m trying to use the ''acts_as_ferret'' gem with Rails. Rails: 1.1.4 and 1.2.3 OS: WinXP I''ve installed both Ferret and the plugin using Ruby Gems: C:\>gem install ferret Successfully installed ferret-0.11.4-mswin32 Installing ri documentation for ferret-0.11.4-mswin32... Installing RDoc documentation for ferret-0.11.4-mswin32... C:\>gem install

Up to now in my ferret development I have been using simple single-word strings as my search queries. I just now am trying to increase the complexity of my queries. When I was passing a single word with no spaces in my index searches, like so: count = index.search_each(''testing'') do |d, s| ... end everything worked fine. But now when I do something like this: count =

I am using Locomotive 2.0.8 with Rails 1.2.3 for development. It works great. I recently installed Ferret 0.11.4 as a gem. The installation seemed to go fine. No error or warning messages. I setup a test rails app to try Ferret, and the server won''t start. The error I get is /Applications/Locomotive2/Bundles/rmagickRailsJan2007_x86.locobundle/

Thanks for the response Jens. Indeed I am sorting by something other than relevancy, so that would explain it. Optimized, it''s extremely fast and handles a good load, but new records kill it until I optimize. I haven''t tried :merge_factor as I wasn''t aware of it. I''m not sure it will help given the above. Regarding the re-index locking code,

Hi, following the discussion about acts_as_ferret on the Rails mailinglist, there was an issue about transactions, which could result in beind the database and ferret out of sync. I have taken a different approach from acts_as_ferret trying to resolve the transaction problem. Instead of adding things to the ferret index in the model, I have added it in the controller. I have only the create part