On Thu, 2006-07-06 at 14:42 -0400, Tim Van Steenburgh wrote: > I'm assuming you're using MySQL with InnoDB... perhaps you > could post > the relevant section of your my.cnf so some of us could take a > look at > it? There's a couple things with InnoDB that can cause > issues. > > Can you expound on this for my (and others') benefit? I'm interested > to hear some of the details.
The big one that jumps to mind is the fact that you must specify in advance how large tables can become: For example: ''' innodb_data_file_path = ibdata1:10M:autoextend:max:128M ''' This creates a 10Mb database that will autoextend up to 128Mb. If you exceed 128Mb you will start seeing undesirable behaviour from MySQL (ranging from crashes to high utilization, tons of log messages, etc, depending on your MySQL version). You don't have to specify the max, but many default configurations do (and if I understand correctly, autoextend only works for one file/tablespace, the last one specified). This is where people often get bit. You really need to read and modify the default my.cnf that is shipped with your distro. There are other settings that can cause issues, either performance-wise or resource-consumption-wise. For example on Gentoo the default my.cnf "optimizes" innodb for use on 64Mb servers: ''' # don't eat too much memory, we're trying to be safe on 64Mb boxes. # you might want to bump this up a bit on boxes with more RAM set-variable = innodb_buffer_pool_size=16M # this is the default, increase if you have lots of tables set-variable = innodb_additional_mem_pool_size=2M ''' Clearly on a more realistic server with 2Gb of RAM, this is going to be suboptimal. I'm not a MySQL expert, but I've been bitten by this stuff on shared hosting boxes I manage. See these pages for reference: http://dev.mysql.com/doc/refman/4.1/en/innodb-configuration.html http://dev.mysql.com/doc/refman/5.0/en/innodb-configuration.html Of course, what I personally recommend is to use PostgreSQL instead and not have to worry about this sort of thing. MySQL has certain advantages (speed and simplicity in exchange for data integrity) when using MyISAM, but the minute you switch to InnoDB things tilt drastically in PostgreSQL's favor. Regards, Cliff --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
