[Xapian-discuss] Xapian under 360 MB VPS

[Kevin Duraj]

Please do not add any file locking in Xapian's read mode. Searches on
Xapian index would become lot slower if processes would have to
negotiate between themselves, which one will lock file first. There is
not file locking necessary when using BerkeleyDB in read mode
therefore Xapian should follow this standard. We already have one slow
search engine Lucene on the market. We do not need to make Xapian the
second Lucene.

Thanks,
Kevin Duraj

On Thu, Jan 21, 2010 at 2:18 PM, Olly Betts <olly at survex.com> wrote:
> On Thu, Jan 21, 2010 at 05:19:41PM +0000, Richard Boulton wrote:
>> 2010/1/21 Marlon Baculio <mbaculio at hotmail.com>:
>> > 1. Will file handle limitation be a problem for multithreaded Xapian reader?
>>
>> Depends on search load.  Each reader keeps about 5 filehandles open,
>> so multiply that by the number of concurrent readers you want.  If it
>> comes close to the per-process fd limit, you've got a problem.
>
> "About 5" is between 3 and 7 for flint, the default backend in 1.0.
>
> The tables for values, spelling, synonyms, and positional data are optional
> and created lazily if such data is actually added to the database.
>
> The per-process fd limit is pretty high on most modern OSes, and can often be
> increased so it's probably not an issue for most people.
>
> Cheers,
>    Olly
>
> _______________________________________________
> Xapian-discuss mailing list
> Xapian-discuss at lists.xapian.org
> http://lists.xapian.org/mailman/listinfo/xapian-discuss
>