Just realized that back in May of last year I accidentally created a DB migration that deleted my index that makes threads and finding replies significantly faster. I'm not sure how that happened but it's the main culprit of slow notifications.
It also just slows down everything on the site period. We use these "tree" queries everywhere and they were completely unoptimized after that index was deleted. DANG.
It seems like the search is no longer sorted in reverse chronological order, its like a mixed bag
It’s sorted by relevance and always has been. How do you want it sorted?
I like cointastical's suggestions. Honestly I hadn't given it much thought. I was searching for something in particular and expected it to show up first because it was the most recent. Its probably shouldn't be as simple as chronological order as I suggested. You should consider integrating a mind-reading library.
You should consider integrating a mind-reading library.
😂 What was the term you used and what were you searching for? It's good to have cases to test when I tune search.
I'll let you know the next time I'm searching for something and how I think it should have showed up. I can't remember exactly what I was doing at the time, I should have mentioned it when I wrote my original comment...
One thing I was searching for that I couldn't find was this 'daily discussion thread'. I searched for 'daily' and didn't see it come up for me to find this post. There was something more specific I was looking for before that that prompted me to find this thread because I thought maybe the behavior changed because of indexing.
It shows up in reverse chronological order, but doesn't include the latest so I needed to grep like an animal
Ah, I see what you mean. I can definitely improve that search.
I know this isn't the way it works now but:
My preferences:
First search results are only where the match is in the title (i.e., come before any results where the only match is in the body), and of those, in reverse chronological order.
An example where I see improvement needed. Search for: fiatjaf
Why would a post from half a year ago come before one from yesterday? How could that one have been deemed to be more relevant?

Exact search:
Matches for exact search (in quotes) would come before any that are relevant that do not have that exact phrase.
Example: "private key"
Why would a comment reply that has only "256 bit key" come before some other comment reply that has an exact match, "private key"?
I'm assuming this is because exact search isn't supported and my search is eseentially identical whether I used quotes (phrase) versus just searched on the two words.

Search of URL or domain:
I want to search on a specific URL, or maybe just a domain and see all Link Posts for that URL or domain, in reverse chronological order).
Example: bitcoinmagazine.com
I want to see the most recent Link posts that are for a link to bitcoinmagazine.com
of course, if I provided a specific URL, I am looking for just that URL (or at least, any URL that include that.
Example: reddit.com/r/bitcoin
Only include in the search results matches from r/bitcoin (which also includes other subdomain prefixes, such as old.reddit.com/r/bitcoin/xxxxxxx )
Oh, and after Link posts, the next set of results should be Description posts where that URL or domain matched in the description. In other words, posts come ahead of comments/replies, but of posts, Link posts with a match come before Description posts with a match.

After that, by relevance is fine. But maybe eventually add a drop down or something where I can request sort "by most recent" or whatever label reverse chronological is given.
Many of these needs with SN's search are now resolved:
SN release: search filters #83923
And, just to help emphasize the importance of useful search:
twitter search is my favorite feature (and undervalued)