New answers tagged database-tuning
Total, but remember that is only a rule of thumb. Use common sense when setting the value. InnoDB does like as much memory as possible, but there are a couple things to consider: 1) Make sure there is enough RAM left over for everything else that needs to run on the server 2) Remember that the point of the InnoDB buffer pool is to handle the normal working ...
InnoDB log files are stored on disk and so consume disk space - http://dev.mysql.com/doc/refman/5.5/en/innodb-configuration.html. However the innodb_buffer_pool_size does impact memory usage. I find this a good reference for memory sizing - http://www.mysqlcalculator.com/
for security, you want your data duplicated on many servers as possible, so if one falls, the others can share the load. "classic" oltp databases performance issues raise from concurrent transactions. Due mainly to locks, time/transaction grows exponentially. Hence, a simple way to mitigate this issue is to have multiple databases, as there will be less ...
Performance considerations say you should have related tables in a single database. Security says you should separate concerns by need, but within a single database you can still maintain that separation via schemas. Separating data for the sake of some unknown reason that is not tested makes no sense. High availability probably says one should try to ...
there is also one more important thing: run explain like this: explain (costs true, analyze true, buffers true) SELECT ... maybe it is related to caching behavior or so. can you post that as well? many thanks, hans
Top 50 recent answers are included