Zeggy Posted January 29, 2011 Share Posted January 29, 2011 Here's a free online guide to database performance: http://use-the-index-luke.com/ You can also download it as an e-book: http://sql-performance-explained.com/ Quote Link to comment Share on other sites More sharing options...
a_bertrand Posted January 30, 2011 Share Posted January 30, 2011 It is certainly important to use correctly the index (as well as the right DB engine), however I would personally first think about my own code and for example avoid 100 queries within a loop and replace it with a single query (if possible). That has too a major impact. Quote Link to comment Share on other sites More sharing options...
Zeggy Posted January 30, 2011 Author Share Posted January 30, 2011 That is poor code, not poor database performance ;D Quote Link to comment Share on other sites More sharing options...
rulerofzu Posted January 30, 2011 Share Posted January 30, 2011 I was discussing mysql recently. A common error with creating mysql tables is the use of INT where people immediatly just opt for int(11) when the value is never going to reach that amount for a very very long time. So you have mediumint which is a much better option or use tinyint where appropriate. Same applies with varchar where people just go for varchar(255) when they should think about what they really need varchar(64) will that suffice? The actual overhead is small and people may think...ah is it worth bothering about. But if you build a game and it becomes a success any small overhead then becomes a very big overhead. Quote Link to comment Share on other sites More sharing options...
a_bertrand Posted January 30, 2011 Share Posted January 30, 2011 True Zeggy but honestly I saw so much of such bad practices that I would say it is the first thing to solve ;) Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.