Please allow Search to look for words 3 letters and greater instead of 5!
#1
01-26-2002, 07:31 PM
Join Date: Nov 2000
Location: Medford, MA, USA
Posts: 25
Likes: 0
Received 0 Likes
on
0 Posts
#2
01-26-2002, 09:21 PM
F150online
Founder
Founder
Join Date: Nov 1996
Location: Roswell, GA USA
Posts: 3,008
Likes: 0
Received 0 Likes
on
0 Posts
https://www.f150online.com/forums/sh...threadid=64055
Please read the forums before posting a question.
Please read the forums before posting a question.
#3
01-26-2002, 10:14 PM
Join Date: Nov 2000
Location: Medford, MA, USA
Posts: 25
Likes: 0
Received 0 Likes
on
0 Posts
...
I guess it comes down to whether the search functionality is important or not, since I think it is and 3 gig for indexes (I'm sure it's much bigger since the thread you list was back in '99) is cheap these days, I would put up with a day of non-search functionality so all those wonderful indexes can be rebuilt and frustration levels (at least mine) would go down. Hey, I'd even pitch in and donate a few bucks for the hardware (if needed).
BTW, I did try using wildcards but still get too many hits on irrelevant threads.
Thanks!
Ron
BTW, I did try using wildcards but still get too many hits on irrelevant threads.
Thanks!
Ron
#4
02-06-2002, 11:36 AM
Senior Member
Join Date: Feb 2002
Location: The nations blunder FLORIDA!!!
Posts: 157
Likes: 0
Received 0 Likes
on
0 Posts
#5
02-09-2002, 01:01 AM
Senior Member
Relax folks...
Chill out a little guys... Steve's experiencing some server load issues that he's been trying to resolve. I've been following his progress on another site on this issue.
RonLariat... A little primer in databases for ya... While 3 gigs is penuts these days, it is still HUGE for a database index. 3 gigs on the database itself is nothing, but a 3 gig database index is an eternity, especially for a word search index.
Why is it such a big deal? Quite simple in fact. Since it is an index, and since we're performing a word search it requires a good part of that index to be read and compared. When you're talking a 3 gigabyte index this takes time and CPU horsepower, just try copying a 3gig file and see how long it takes.
Better yet if you are you running windows 98 or later, try searching your hard drive for all files containing "ford truck".. After anywhere from 1-10 minutes (depending on drive size and speed) it should finish. This obviously puts a tremendous strain on the server, especially if there are dozens of people searching at the same time.
The reason Steve went from 3 to 5 words is to cut down on the size of that index to reduce disk overhead. Once he tracks down the problems he'll be able to go back to the 3 word searching again. It just requires patience.
RonLariat... A little primer in databases for ya... While 3 gigs is penuts these days, it is still HUGE for a database index. 3 gigs on the database itself is nothing, but a 3 gig database index is an eternity, especially for a word search index.
Why is it such a big deal? Quite simple in fact. Since it is an index, and since we're performing a word search it requires a good part of that index to be read and compared. When you're talking a 3 gigabyte index this takes time and CPU horsepower, just try copying a 3gig file and see how long it takes.
Better yet if you are you running windows 98 or later, try searching your hard drive for all files containing "ford truck".. After anywhere from 1-10 minutes (depending on drive size and speed) it should finish. This obviously puts a tremendous strain on the server, especially if there are dozens of people searching at the same time.
The reason Steve went from 3 to 5 words is to cut down on the size of that index to reduce disk overhead. Once he tracks down the problems he'll be able to go back to the 3 word searching again. It just requires patience.
#7
02-20-2002, 08:40 AM
Join Date: Nov 2000
Location: Medford, MA, USA
Posts: 25
Likes: 0
Received 0 Likes
on
0 Posts
Y2K OffRoad:
Thanks, but I don't need a db primer, I've been an active database developer since the early 80s and currently am a developer for a HUGE database company and I write (with others) the ODBC, OLEDB and JDBC drivers for them. We are currently developing a J2EE Connector. BTW, 3gig indexes, while they may be huge are not uncommon these days.
Ron
Thanks, but I don't need a db primer, I've been an active database developer since the early 80s and currently am a developer for a HUGE database company and I write (with others) the ODBC, OLEDB and JDBC drivers for them. We are currently developing a J2EE Connector. BTW, 3gig indexes, while they may be huge are not uncommon these days.
Ron