Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

SI - Site Forums : Silicon Investor - Legacy Interface Discussion (2004-2011) -- Ignore unavailable to you. Want to Upgrade?

To: Peter Dierks who wrote (2884)	12/10/2004 11:15:12 AM
From: SI Bob	Read Replies (1) \| Respond to of 6035

Last night I'd made a structure change to the search tables to save space and speed up searches. And completely spaced out that doing so to the current-year search table would break the posting routine. The quick fix was to have the system not update the search table until I can fix the update routine to take the structure change into account. When I get that done, I'll be able to run a query that'll quickly get the search table caught up. However, while I was at it last night, I also (apparently unwisely) fired off the database shrink routine to take advantage of the sizable space savings I'd found. Problem is, it's been running since late last night and still is running, and keeping CPU utilization on the db server pretty high (40%+ area), so I suspect there are probably timeouts happening here and there, and it makes sense that it could be happening most often with Advanced Search and Preview/Spellcheck, which both need a lot of resources. The latter especially with large messages. At least, I hope that's the explanation. I'll try posting this through Preview and see what happens. Edit: Worked fine. And very quickly. And the Shrink job aborted. It encountered a deadlock and was chosen as the victim. That's pretty surprising. However, the db's CPU is still pretty busy this morning. I'd made the structure changes to the 97, 98, and 99 search tables. It didn't occur to me to mark those tables as never needing search updates since they're static, so the system is busily rebuilding those search catalogs. It looks like in about an hour, one of them will be done and the other two in about 2 hours. Right now I'm going to fix the current-year updater and let it rebuild that catalog. I just checked and its entry count is zero and, sure enough, doing Public Message search on anything (that would include Advanced Search using the current year) yields no results.