Yeah, I know-- this sucks. The solution as far as I can tell is for us to convert our 3 search tables (50k, 8M and 272k rows respectively) over to InnoDB which all references indicate will give us the performance we want by allowing us to have row level locking. But it's a time intensive process that will require taking the server down for a bit while we monkey around in the database (we need to make some adjustments to the way that MySQL stores its data files before converting this stuff to InnoDB or we'll wind up with some InnoDB files that are just too large for us to reasonably handle. It takes time, and those of us with the time and the access have been up to our ears trying to get 2.2 ready for a release candidate.
Sorry. Wish I could give you a firm date for when we'll make the conversion, but I don't have anything to offer up at the moment. The only other option we have is to turn search back on again and let the site just get hammered periodically. :-/ Suggestions?
chmac
Joined: 2006-11-02
Posts: 8
Posted: Thu, 2006-11-02 11:19
Could the community help with this? I have a friend who works for MySQL, he gets paid to do so many community hours a month, he might be able to help, I could provide the beer to encourage the transaction... Presumably the site needs to go down for a period while the transfer is done? He's in Bangkok so that might work for picking a good time of the day.
If the site has to go down for even 24 hours to bring back the search facility, I'd say it's worth it. If it's not that simple, what about limiting the number of searches? Something simple maybe, a cookie that says the time of your last search:
if ($_COOKIE['search_time'}+60 > now()) {
die('Sorry, to reduce the load on the servers we only allow one search every 60 seconds, please try again in a minute.');
}
Search is back! I converted our database over to InnoDB which should take care of our table locking issues. Performance isn't as good as Google, but it's got much better integration. Give it a shot! Thanks for bugging me and reminding me to fix it
chmac
Joined: 2006-11-02
Posts: 8
Posted: Sun, 2006-11-05 10:14
Great, thanks a milling, fab to have it back online!
Posts: 13451
Normally you use the search link on the navbar above, but search is currently disabled for performance issues.
h0bbel - Gallery Team
If you found my help useful, please consider donating to Gallery
http://h0bbel.p0ggel.org
Posts: 32509
well, google search works pretty well IMO.
and that's what the current search function on this website is doing.
Posts: 13451
I forgot to mention that, didn't I. Oh well.
h0bbel - Gallery Team
If you found my help useful, please consider donating to Gallery
http://h0bbel.p0ggel.org
Posts: 6
more than 2 weeks to resolve performance issues?
Posts: 13451
Yes.
h0bbel - Gallery Team
If you found my help useful, please consider donating to Gallery
http://h0bbel.p0ggel.org
Posts: 8
What's the story morning glory? Are the performance issues resolved yet? No forum search must be generating a whole bunch of unnecessary posts...
What about search limiting? Only 1 ever 60 seconds. It bugs the hell out me personally, but it's better than nothing...
CM.
-----
Blog: http://www.callum-macdonald.com/
Posts: 7994
Yeah, I know-- this sucks. The solution as far as I can tell is for us to convert our 3 search tables (50k, 8M and 272k rows respectively) over to InnoDB which all references indicate will give us the performance we want by allowing us to have row level locking. But it's a time intensive process that will require taking the server down for a bit while we monkey around in the database (we need to make some adjustments to the way that MySQL stores its data files before converting this stuff to InnoDB or we'll wind up with some InnoDB files that are just too large for us to reasonably handle. It takes time, and those of us with the time and the access have been up to our ears trying to get 2.2 ready for a release candidate.
Sorry. Wish I could give you a firm date for when we'll make the conversion, but I don't have anything to offer up at the moment. The only other option we have is to turn search back on again and let the site just get hammered periodically. :-/ Suggestions?
Posts: 8
Could the community help with this? I have a friend who works for MySQL, he gets paid to do so many community hours a month, he might be able to help, I could provide the beer to encourage the transaction... Presumably the site needs to go down for a period while the transfer is done? He's in Bangkok so that might work for picking a good time of the day.
If the site has to go down for even 24 hours to bring back the search facility, I'd say it's worth it. If it's not that simple, what about limiting the number of searches? Something simple maybe, a cookie that says the time of your last search:
if ($_COOKIE['search_time'}+60 > now()) {
die('Sorry, to reduce the load on the servers we only allow one search every 60 seconds, please try again in a minute.');
}
Just thinking out loud, that code may not work!
C.
-----
Blog: http://www.callum-macdonald.com/
Posts: 7994
Search is back! I converted our database over to InnoDB which should take care of our table locking issues. Performance isn't as good as Google, but it's got much better integration. Give it a shot! Thanks for bugging me and reminding me to fix it
Posts: 8
Great, thanks a milling, fab to have it back online!
-----
Blog: http://www.callum-macdonald.com/