similar to: problem with queries

> > p.s. For an in depth analysis of TCP_CORK read Christiopher Baus' excelent > article: http://www.baus.net/on-tcp_cork Thanks for this pointer. I'd been meaning to reply on this thread, but hadn't got around to it, primarily because I didn't really understand TCP_CORK (the linux manpage is, as usual, fairly unclear on what exactly it does). Now I understand! > >

Dear all, It seems there''s a sort bug with ferret 0.10.9 on Debian. I sort the search results by a field which can contain null values. The string sort type doesn''t work. If I test the values and replace null by empty strings when indexing, it works. Johan Analyst Programmer Belgian Biodiversity Platform ( http://www.biodiversity.be) Belgian Federal Science Policy Office

Klaas Jan Wierenga wrote: > Hi Henri and others, > > Very interesting post about TCP_CORK. I would be very interested in having > it applied in the next version of Icecast. I'd be more interested in some figures to show there being a benefit, most examples talk about HTTP servers with short lived connections where sendfile(2) is used. > For low-bitrate streams the problem

Dear all, I have a table with a column named "type" and I ''d like to access the type field of the correspondant model object but I get a deprecation warning when I use the following code : modelObject.type "type deprecated use class instead" How can I access such a named field in rails ? Johan Johan Duflost Analyst Programmer Belgian Biodiversity Platform (

Is there a fast way to determine how many documents a term occurs in, besides iterating through every document with TermDocEnum? -- Best regards, Stian Gryt?yr

Dear list, I ''m using a text input field with autocompletion . The suggestions come from a ferret index which is created by getting all the terms belonging to other indices. Here is the code: class Suggestion attr_accessor :term def self.index(create) [Person, Project, Orgunit].each{|kl| terms = self.all_terms(kl) terms.each{|term| suggestion =

We're abusing icecast in a true narrowcasting setup (personalized stream per mountpoint). The streams itself are created in a piece of proprietory (spelling?, i'm dutch) software, icecast merely relays them. However, the intended endpoint is an embedded device. This device has trouble with tcp/ip packets not matching the max. packet size (MSS or MSS minus header). After eleborate testing,

I''m fairly new to ferret / aaf and finding it much easier to use than HyperEstraier (which I migrated from). However, I am getting a few errors and I need to figure out if they''re problems with my usage of ferret or a bug I should report. I''m currently running Ferret 0.10.11 with acts_as_ferret (latest via svn external) and 3 times today I''ve seen the

> This is exactly why it was implemented, a few people complained about > the overhead with large numbers of listeners, not only because of the > TCP overhead but also the fact that it reduces the write syscall > overhead. Will TCP_CORK (linux) and TCP_NOPUSH (BSD) give noticable > benefits wrt icecast? It might prove helpful if available but more info > is needed. As

Klaas Jan Wierenga wrote: >>This is exactly why it was implemented, a few people complained about >>the overhead with large numbers of listeners, not only because of the >>TCP overhead but also the fact that it reduces the write syscall >>overhead. Will TCP_CORK (linux) and TCP_NOPUSH (BSD) give noticable >>benefits wrt icecast? It might prove helpful if available but

Hey guys, I''ve just removed the -fno-stack-protector flag from the release so those who had trouble because of this should now be able to install 0.11.2-rc3. If you have any problems with this release, please let me ASAP. Cheers, Dave -- Dave Balmain http://www.davebalmain.com/

Hi, I just checked out ferret 0.10.14 from subversion and am getting intermittent failures from the thread_safety_index_test.rb script. Sometimes it runs through to the end with no errors, but other times I get errors, including segfaults. I reported the bug here: http://ferret.davebalmain.com/trac/ticket/153 Can anyone else reproduce this? svn co

Hi Henri and others, Very interesting post about TCP_CORK. I would be very interested in having it applied in the next version of Icecast. I'm using Icecast in a somewhat narrowcasting setup with large numbers of sources (> 100) and between 5 and 50 listeners per source. All streaming is done at low bitrates (16 - 24 kbit/sec) and listeners use embedded devices connected by 56k modems. It

Hi, I''ve adapted my ferret_killer1.rb script to reproduce the segfaults I''m still having in my app with Ferret 0.11.3. ferret_killer1 didn''t reproduce these - I had to add code to retrieve the documents from the index after searching (and fixed the index creation bug Dave spotted). http://johnleach.co.uk/downloads/ruby/ferret/ferret_killer3.rb To use, in one terminal

Michael, With regard to your comment below: > As a streaming server, it's fairly crucial for icecast to send out > data with as low a delay as possible (many clients don't care, but > some do). That's why we use TCP_NODELAY - we actually WANT to send out > data as soon as we can. Can you explain how some clients depend on a low delay when receiving data from icecast? How

Hi ferreteers, I came across a segfault in the query parser. It had already been reported[1] and fixed[2], but it can lead to a denial of service. If you use Ferret anywhere that you allow users to execute queries, those users can crash your Ruby process with a specially crafted query. I''m sure you''re all using Monit or something for your Rails or drb processes, so

Hi dave, and everyone ;) I''ve finished my extension to export Index.search(..) loaded results into json. Here''s a little benchmark of what i''ve done : >> Benchmark.realtime { INDEX.search(query, :limit => 1000).hits.each { |x| INDEX[x.doc].load.to_json } } => 7.38711595535278 >> Benchmark.realtime { INDEX.search(''type:hardware'',

Hi folks, Just thought I better let you all know that I''m still working on the next release of Ferret. I''ve been working the last 7 days doing nothing but Ferret development. The last iteration generated a diff of almost 5000 lines so there are some pretty major changes. Most people won''t notice these changes however as the API remains unchanged. But if you were having

Hi, I have a many-to-many relationship between two tables, questions and answers. My MySQL schema for the link table creates a primary key from the two fields to prevent duplicate records. When I add the same answer to the same question more than once, rails attempts to create a duplicate record and explodes with a MySQL error: MysqlError: Duplicate entry ''3-3'' for key 1:

Dear all, Does anybody know if there''s problem with ferret running with mongrel ? I got unpredictable segfaults. Everything works well with fastcgi instead of mongrel. I use ruby 1.8.5, apache 2, mod proxy, mongrel 0.3.13.4, ferret 0.10.13 and rails 1.1.6 Thanks, Johan Johan Duflost Analyst Programmer Belgian Biodiversity Platform ( http://www.biodiversity.be) Belgian Federal