Lucene is not slow, only the Zend PHP re-implementation of the Lucene
file format + search.
In my opinion it's close to unusable for real life scenarios (large
data set, fast indexing ...).
It probably would work ok for a small dataset such as < 10000.
I recomend Solr as alternative which is Java Lucene service + XML API
for access (and much more).
As for the search part you need to define your exact document model,
the basic entity used in search is the document
that has several properties. There is usually one field to be used for
full text search and several other fields that
you use for structured search (e.g. date, tags).
gabriel
On Jun 1, 8:13 pm, comb <[email protected]> wrote:
> Hi!
>
> I have 5 different Models that I want to be searchable.
> I don't know, how to implement the search right now. First thing I
> think of is Zend Lucene, but I read several times, that the
> performance is bad (cannot use the java implementation).
>
> No my question is: where is the limit of Zend Lucene? I expect about
> 1000-10.000 records per Model and a maximum of 100 search-requests per
> minute. (probably 1-10 per minute average)
> Can Zend Lucene handle that amount?
>
> Is there an other (PHP-)library that I could do the searching with, if
> Lucene is to slow?
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
