tag:blogger.com,1999:blog-4830674838175229017.post8197450532701048871..comments2017-03-27T07:01:17.527+01:00Comments on The keyword geek: Precomputing for fun and profitJennyhttp://www.blogger.com/profile/17369789355356245733noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4830674838175229017.post-49081176711781389162011-08-15T16:08:57.621+01:002011-08-15T16:08:57.621+01:00I dread to think what would happen with concurrent...I dread to think what would happen with concurrent queries on this one, it takes minutes with just me. But it does do some significant querying on very large data sets. <br /><br />I've wondered whether I could craft some incredibly clever take on the SQL that did the queries much more quickly, but you can't escape that it's a huge amount of data to sift.Jennyhttps://www.blogger.com/profile/06245532899446693235noreply@blogger.comtag:blogger.com,1999:blog-4830674838175229017.post-73216354522230929032011-08-15T15:53:25.836+01:002011-08-15T15:53:25.836+01:00Heh, I had a similar thought recently re online tu...Heh, I had a similar thought recently re online turn-based games. The first large-scale DB-based game that I designed, we ended up saving out flat files holding all the turn results, because the pgSQL server couldn't serve out query results fast enough when all the players wanted to see what had happened.<br /><br />As time went on, processors becoming faster and RDBMSes (and my coding ;-) Mohttps://www.blogger.com/profile/18147500197867245726noreply@blogger.com