ãµã¤ãã¦ãºã¯ã¯ã©ã¦ããã¼ã¹ã®ã°ã«ã¼ãã¦ã§ã¢ãæ¥åæ¹åãµã¼ãã¹ã軸ã«ã社ä¼ã®ãã¼ã ã¯ã¼ã¯åä¸ãæ¯æ´ãã¦ãã¾ãã
ãã¡ã¤ã«ãµã¤ãºã 1/10 ã«ãªã£ã¦ã¢ã¯ã»ã¹é度ãå¤§å¹ æ¹åããå®ãã¼ã¿ã§ããã¯ããã㪠*1ã Iâve tried to convert this table using COMPRESSED row format. This time conversion took 1,5 hours and results were really surprising: Only 5Gb data file (from 60Gb) ~5% I/O load according to iostat (from 99%) ~5% CPU load according to top (from 80-100% mostly waiting for I/O) 0.01 sec average lookup time by primary key (from 1-20 sec before the conve
Database Optimization for Rails Apps 20th Nov 2007 by Gwyn Morfey Summary Use STRAIGHT_JOIN if MySQL is doing something silly MySQL Datetimes are not slow MyISAM is much, much faster than InnoDB Consider MySQL partitioning; it's not hard Watch out for background optimisation and query caching Log everything you do, and why The reporting application I'm working on does a date-range select against a
ã©ã³ãã³ã°
ã©ã³ãã³ã°
ã©ã³ãã³ã°
ãªãªã¼ã¹ãé害æ å ±ãªã©ã®ãµã¼ãã¹ã®ãç¥ãã
ææ°ã®äººæ°ã¨ã³ããªã¼ã®é ä¿¡
å¦çãå®è¡ä¸ã§ã
j次ã®ããã¯ãã¼ã¯
kåã®ããã¯ãã¼ã¯
lãã¨ã§èªã
eã³ã¡ã³ãä¸è¦§ãéã
oãã¼ã¸ãéã
{{#tags}}- {{label}}
{{/tags}}