On one specific MT(3.35) install, when searching I'm getting a very slow response and a 500 error - which I consider due to the host server timing out.
It's a relatively tiny (3.2meg and 379 entries) SQL database.
Internally, from the MT interface, search works fine - even something as stupid as searching for a comma lists all 379 entries within seconds. But when undertaken through a browser, the 500 error occurs.
In an effort to recreate the onset of the problem, in a test install I:
Wiped all entries by running the SQL statement TRUNCATE TABLE mt_entry.
Progressively reimported the entries in blocks, then repeated the search for a common term'.
Each slowed the search, until I'd imported around 2.2meg and 244 entries and the search then generated the 500 error after about 10 seconds.
However, in searching for a less common term, results are returned in around 8 seconds.
And, when searching a term which appears in only one entry, results are returned in around 6 seconds.
So, continuing to reimport more entries to a total of around 2.6meg and 291 entries, searching that term which appears in only one entry generates the 500 error after about 10 seconds.
Seems that if it can complete the search within 10 seconds results are returned, but longer than that generates the 500 error.
My host has since confirmed I've reached a limit within their shared host package (and @$20/month from 1&1 it's by no means 'budget' for shared).
I'm about to upgrade hosting, and wondering if anyone has experienced similar, or has suggestions for shared hosting with higher limits (I have clients who could encounter similar issues).