June 19, 2013

Post: Why MySQL could be slow with large tables ?

…,Technocarati MySQL has installations with many billions of rows and delivers great performance. What could be the reason ? The reason is normally table design and…have star join with dimention tables being small it would not slow things down too much. On other hand join of few large tables, which is…

Post: Database problems in MySQL/PHP Applications

… cached lookup table however so you do not have all these problems with loosing data etc. Read more in my Why MySQL Could be slow with Large Tables article. 5. The n+1 pattern This probably should rather be called…

Comment: Database problems in MySQL/PHP Applications

… are different with MySQL. Good design will help dictate how many tables are required in order to get the job done. To be good… cached lookup table however so you do > not have all these problems with loosing data etc. Read more in my > Why MySQL Could be slow with Large Tables article. Deciding…

Comment: Small things are better

…/09/why-mysql-could-be-slow-with-large-tables/ I was just very surprised when reading some of the comments that an alter table on a 500GB (say) table could take up to 2 days!! I have my tables as separate files/table (which I…

Comment: Why MySQL could be slow with large tables ?

Why MySQL could be slow with large tables ?: “If you’ve been reading enough database related forums, mailing lists or blogs you probably heard complains about MySQL being unable to… well known with customers like Google, Yahoo, LiveJournal,Technocarati MySQL has installations with many billions of rows and delivers great performance. What could be the…

Comment: Why MySQL could be slow with large tables ?

[...] Why MySQL could be slow with large tables [...]

Post: Slow DROP TABLE

MySQL into removing smaller files with DROP TABLE to minimize the effect, such as: TRUNCATE TABLE large_table; ALTER TABLE large_table ENGINE=…; DROP TABLE large_table; TRUNCATE TABLE large_table; OPTIMIZE TABLE large_table; DROP TABLE large_table

Post: MySQL 5.5 and MySQL 5.6 default variable values differences

…QUERY_CACHE_SIZE | 0 | 1048576 | | SLOW_QUERY_LOG…could have been made even larger. Write intensive workload will do a lot better on MySQL 5.6 withwhy default value is 9. In any case very welcome change to help workloads with…not belarge number of tables or if you do many create/drop of innodb tables

Post: New SpecJAppServer results at MySQL and Sun.

with them as it could be which makes it better to disable them. The MySQL Settings are probably what is the most interesting: MySQLtable_size=200M log-output = FILE log-slow-queries=/tmp/mysql-slow.log long_query_time = 1 innodb_data_home_dir = /data/mysqllarge