I figured it must be, or you would have done it already. However, by parsing these words at request time you are moving something that is intentionally done ahead (cached, basically) into the request handling. It makes sense that you would pay a performance penalty for that.
First, swish keeps track of word position for phrase matches. But, all sorts of things will bump the position counter, special chars, some html tags, and so on.
What I had in mind was keeping a character index into the original documents, not a a word index.
Right about /o in the regexp. See my comments (and I guess confusion) in my example code...
Sorry, I don't see it. If you need help with /o, there are some very good regex folks on here. I also liked the discussion in the Perl Cookbook about this.
In reply to Re: Re: Re: Context search term highlighting - Perl is too slow
by perrin
in thread Context search term highlighting - Perl is too slow
by moseley
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |