I currently have the non-SQL version installed on a dedicated box (Pentium III-850, 256mb sdram). Nearly 11,000 sites and the links.db file is around 2.5 MB (no extra fields). Still purrs like a new born kitten (watch those claws) - kudos to GT. Searches continue to be blazing fast (albeit via specially modified search script), and no data corruption to date. But the one problem (the obvious one) is building (done via cron). Building is scheduled at midnight, daily. I just arose, and found that the server is still building. Ouch. Mind you, building occurs during non-peak traffic period - no obvious impact on server: pages serve fast and scripts (including search.cgi) execute relatively fast (during build, search for more common [max hits] keyword takes 4-7 seconds). But 7+ hours to build is getting silly. I have now disabled new submissions (and building the database) for the moment as I plan to upgrade to the Links SQL within the month.
For the database (and server) I describe, what sort of time frame would be typical (as a range for example) to cron build via Links SQL? And can you perform [Selective Build] if you use ratings (sites are sorted by rating alone)?
Cheers - Dan
For the database (and server) I describe, what sort of time frame would be typical (as a range for example) to cron build via Links SQL? And can you perform [Selective Build] if you use ratings (sites are sorted by rating alone)?
Cheers - Dan