Symptom of edge n-grams on a cold dictionary. I seeded it from provider names in the hosting directory but the fuzzy threshold is too aggressive. Will tighten the Levenshtein distance and rebuild.
Is 'search first' still valid advice?
200ms is fine for a forum but I just want to know if anyone else's search for "10G switch" is returning knitting patterns. The stemmer is too eager.
Standard analyzer + porter stemmer will do that. "Switch" stems to "switch" but if the index has "switching" from a thread on VLAN trunking, the overlap with textile keywords is nonzero. Custom analyzer with a keyword marker for networking terms would help, but that's a lot of maintenance.
I am try search "how to install docker" and result is very good now. Before I ask same thing and someone say search first but search not work. Now I think search first is OK advice.
Same experience here. I stopped searching because it was faster to ask and absorb the sarcasm. The new setup actually found my own thread from six months ago when I tested it, which was embarrassing but useful.
This.
Has anyone tested whether the search respects the "infrastructure" subforum scope? I searched for "RAID" and got results from marketplace.
Known. The subforum filter is a post-search facet, not a query constraint, because some threads move between subforums and I didn't want to break links. I'll add an explicit
forum:infrastructure operator.
In Madrid we have a saying: "buscar para encontrar" -- search in order to find. But if the finding fails, the blame goes to the seeker, not the library. The old advice was library propaganda.
I'm going to be the one who asks: what was the single node running on before? A Raspberry Pi? 4GB heap suggests something small.