Search down?
um actually don't. The reason search doesn't work is that searches pile up and crash the server. That's why it's disabled at the top. I didn't disable it at the bottom because I forgot it was there.
Search is broken as the 15 other threads here indicate.
Search is broken as the 15 other threads here indicate.
Well now that I said don't use it everyone will try to wring the last possible search out of it before it dies. That's one of the big problems with search, some guy does a search for "berlina black" in 3 forums which basically means make a copy temporary copy of the entire database and scan it post by post. The user thinks it stuck so goes back and hits submit again which makes an other copy temporary copy and so on it goes.
The search will work on very specific and well crafted keywords but that is not what people search for. Searching only specific forums only compounds the problem which is contrary to reason but not logic. Searches against all posts in all forum is orders of magnitude faster.
Until I can find a way for logic and reason to work in harmony search will be broken because what people search for the most is what takes the database the most effort to produce. When you start a search it runs to completion regardless of what you do on your browser. Start 10 searches each taking 10000 seconds or longer to complete and you've killed the server. Each new search makes all the rest slower until it spirals out of control and crashes. It is a snowball of discontent I don't know how to solve within our budgetary constraints.
[geekspeak]
All of the posts are stored in one table (or file). It's like an Excel spreadsheet with 6.5 million rows. When you search on that table you can use only one index or key. An index makes searching way way faster because the database maintains a catalog of key values and can jump straight to them. When you look up a name in the phone book, you first jump to the section for the first letter, and then the next and so on skipping what you don't need. That's indexing in a nutshell.
When you say show me posts matching "berlina black" in forum #1 you are asking to look up all the posts matching "berlina black" and then scan them from start to end for all those which are in forum #1. Searching for something like "berlina black" means match every single post containing any of those keywrords, put them in a temporary file and then scan from start to end picking out those which are in forum #1. Searching for "berlina black s2000" is even worse because the search become less specific not more. You are saying all posts containing "berlina" or "black" or "s2000". More matches, more results, more data to copy, more results to scan, more time.
Searching for "berlina black" takes 23 seconds. Searching for "berlina black" in S2000 Talk takes 23000 seconds. See the disconnect? The more specific you try to make the query the longer it takes. Reason dictates that by limiting the search to a subset of forums you will get better results and there will be fewer posts to look through and thus take less time. It's half right. You will get better results.
[/geekspeak]
The search will work on very specific and well crafted keywords but that is not what people search for. Searching only specific forums only compounds the problem which is contrary to reason but not logic. Searches against all posts in all forum is orders of magnitude faster.
Until I can find a way for logic and reason to work in harmony search will be broken because what people search for the most is what takes the database the most effort to produce. When you start a search it runs to completion regardless of what you do on your browser. Start 10 searches each taking 10000 seconds or longer to complete and you've killed the server. Each new search makes all the rest slower until it spirals out of control and crashes. It is a snowball of discontent I don't know how to solve within our budgetary constraints.
[geekspeak]
All of the posts are stored in one table (or file). It's like an Excel spreadsheet with 6.5 million rows. When you search on that table you can use only one index or key. An index makes searching way way faster because the database maintains a catalog of key values and can jump straight to them. When you look up a name in the phone book, you first jump to the section for the first letter, and then the next and so on skipping what you don't need. That's indexing in a nutshell.
When you say show me posts matching "berlina black" in forum #1 you are asking to look up all the posts matching "berlina black" and then scan them from start to end for all those which are in forum #1. Searching for something like "berlina black" means match every single post containing any of those keywrords, put them in a temporary file and then scan from start to end picking out those which are in forum #1. Searching for "berlina black s2000" is even worse because the search become less specific not more. You are saying all posts containing "berlina" or "black" or "s2000". More matches, more results, more data to copy, more results to scan, more time.
Searching for "berlina black" takes 23 seconds. Searching for "berlina black" in S2000 Talk takes 23000 seconds. See the disconnect? The more specific you try to make the query the longer it takes. Reason dictates that by limiting the search to a subset of forums you will get better results and there will be fewer posts to look through and thus take less time. It's half right. You will get better results.
[/geekspeak]
Thread
Thread Starter
Forum
Replies
Last Post




Oops, trust us to find the "back door". 