I'm using a dedicated box...
Intel Core 2 Duo E7500 2.93GHz
2048 MB Memory
CentOS 5 (64bit)
This is an advanced question for WP pros. I have a test installation that I was kicking around. I'm using an RSS feed to populate custom post types(jobs) and when using the search, and when including in that search a custom field or 2, the search becomes all but dead.
Am I pushing the limits of WP too hard?
Am I pushing the limits of my Dedi box too hard?
A little of both?
Do I need to use the search filters to fully customize my search, bypassing the core, using indexing and or creating separate tables for a more custom search?
It seems that with the structure of the postmeta, I will always need an inner join (if I need 2 or more results(custom fields) in a single post from this table) and this is a resource buster for sure.
At 50k-80k posts I would get results back in 1-3.5 seconds with no other server load.
At 250k-280k posts my the script times-out. I make time-out adjustments and the search has given results after 20 seconds or more with no other server load.
While using the search for posts in the back-end(admin section) and no other filters to the search query(no extra postmeta query inclusions on my part), I get results in about 5-10 seconds with 280k posts in the system.
If I actually had traffic, this would all be bad. right?
Has anybody come across search query fixes for large amounts of data in WP?
Thanks in advance for any input at all.