Hi Daniel,

Could you give a very rough, 'ball park' figure regarding your 'performance on large systems' warning.

Does it depend on the searched CCK field's configuration much? Multiple values etc.

I realise this is nearly a 'how long is a piece of string' question, but you probably have something in mind and experience of the issue, so *any* feedback would be appreciated.

Thanks.

Comments

danielb’s picture

danielb commented

Hang on, it's not a warning, per se. I haven't seen any performance issues. It's just that if you look at the theory of the two modules, NQF and this one, NQF uses an index in the database so technically it should be very efficient for matching the start of node titles. I don't know what capacity you would need before it starts to be an issue though.

Basically with Autocomplete Node Finder if you have n records, it will check n records. NQF can quickly discard titles that start with the wrong letter etc...

I am using it on 600 nodes with no speed problems.

I will be putting it on a much larger site next week, if it becomes slow I have a few ideas on how to speed it up by building a custom search index for the fields you are using in the module - but depending on what kind of data you were searching on it may create too much overhead.

tebb’s picture

tebb commented

Sorry Daniel, perhaps I should not have used the word 'warning' and I misunderstood the implication of the project page section being italicised.

My need is a way off yet, but will not be to search from the beginning, but within the content of one or more fields, so I wanted to know how applicable this module would be. It sounds spot on.

Thanks for your work the quick response to my question.

danielb’s picture

danielb commented
Status: Active » Fixed

OK, good point about the italics.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.