May 22, 2012

Post: Why MySQL could be slow with large tables ?

database related forums, mailing lists or blogs you probably heard complains about MySQL being unable to handle more than 1.000.000 (orbetter than others. For example if you have star join with dimention tables being small

Post: Recovery beyond data restore

have many trashed copies to deal with. If you have just one or several small tables corrupted you can reload them. One option is tolarge portion of data trashed you may need to recover full database on all slaves which is best done in binary mode for large

Post: High-Performance Click Analysis with MySQL

better-ness in the meantime, you might have to do some awkward backpedaling with customers, who now expect realtime data.  The databaseOne reason denormalization is important is that nested-loop joins on large data sets are very expensive.  If MySQL supported sort-merge or

Post: Database problems in MySQL/PHP Applications

to have very simple logic besides database – in most cases you would have… ALTER TABLE or OPTIMIZE TABLE now locks small table…have all these problems with loosing data etc. Read more in my Why MySQL Could be slow with LargeMySQL you might be better of using several queries than doing complicated ones

Post: New SpecJAppServer results at MySQL and Sun.

database ? Or does it mean MySQL did not scale well tohave queries which only do small sorts it is indeed better to haveone. So the it was better to restrict amount of dirty pages Innodb can have to get better performance. It probably was done to

Post: MySQL Query Cache

to implement. Might not work with transactions – Different transactions may see different states of the database, depending on the updates they havehave change their result set but MySQL has no way to identify which oneor timeout based invalidation which can offer much better

Post: Heikki Tuuri answers to Innodb questions, Part II

mysql.com/bug.php?id=29560 Concerning a switch to Oracle’s main database, I believe different applications work best on different databaseto get large data manageable. MySQL Master Master Manager can help you to automate it a bit. I also like to keep tables small enough, “sharding” to

Comment: Database problems in MySQL/PHP Applications

to have very simple logic > besides database – in most cases you would haveor OPTIMIZE TABLE > now locks smallMySQL you might be > better of using several queries than doing complicated ones

Post: Cache Performance Comparison

to access same data read from database multiple times. Examining MySQL full query logs from many applications seeing severalto performance of all in memory caches and so you might be betterhave just one web server or your data set is small

Post: FaceBook Search, Search for social networks

to be indexed available for index process. With Sphinx which talks directly to the MySQL databaseto know exact number if it is largesmall numbers are however need to be exact to be able toor something else which gives me best profiles) I would likely get much better