Hi,
firstly thanks for a great module. Wouldn't know what to do without it! Secondly a feature request for the Search Lucene API. I have found that hook_init loads Search Lucene on every page request, no matter if Search Lucene is actually used. In my profile log Search Lucene API is eating about 100ms (this is an obviously bloated value because the profiler is running) during every page generation. I would suggest you put all the actual loading of zend components and registering of autoload paths and so forth into an extra function, which is called if an actual search request or search index update is performed. I don't know much about the structure of your code or how easy this is to implement, so please take this as a suggestion which may be implemented if a maintainer wants to spend work on performance optimization.
Did I mention you did a great job on this?
Thanks
Comments
Comment #1
yngens commentedsubscribe
Comment #2
jacobpov commentedsubscribe
Comment #3
cpliakas commentedHi huesforalice.
Thanks for the kind words. I agree with you 100% that this could be optimized. It will take a little bit of work to get us there, but I think it can happen. The 7.x-3.x version of Search Lucene API will make use of "adapters", for example a "Zend Framework" adapter for the PHP port of Lucene as well as an "Elastic Search" adapter to allow this module to scale by integrating with an external service. Therefore, the architecture should improve helping the implementation of this feature.
Thanks,
Chris
Comment #4
cpliakas commentedOther related tasks for the PHP version of Lucene are #812102: Implement a term frequency cache and #812106: Implement search methods that allow for true filters. Changing to a task and postponing for consistency with other 3.x tasks.
Comment #5
cpliakas commentedDue to end of life announcement.