Originally posted by Daemon Sin
Surely if you set up a cron for it you'll be pulling all the data from the games db to save in the new games explorer db. Which means when you're doing the update you'll be slowing the performance on the normal games db.
You could be right, depending on the number of moves made per day.
Though it should be noted that most database tables are optimised for
read operations, rather than write operations. That means, the load on
the database server will be considerably less if you read the moves
made since the last update (not the entire database)
temporary table, and then write to the separate gamesexplorer
database, as opposed to read and write into the same database.
Another solution is to have a mirror server, where every change made to
the real games database is sent over to the mirror server. This would
happen in the background during idle time, so it wouldn't affect the
performance of the site, and the cron script would then have a complete
copy of the real games database to work with on the side.
I'm saying there are solutions to this problem, but whether they're worth
the time, cost and effort, I would assume is dependant on how many
people will actually use this feature.