… DESC; LucidDB: 7.351 seconds InfoBright: 2.92 sec MonetDB: 0.5 sec – Q6: SELECT t.”Carrier”, c, c2, c*1000/c2… 1y, 6.76s, 1.74s, 0.55s 2y, 28.82s, 3.68s, 1.10s 3y, 35.37s, 5.44s, 1.69s 4y, 41.66s, 7.22s, 2.12s 10y, 72.67s, 17.42s, 29.14s – Q9: select “Year” ,count(*) as c1 from “ontime” group by “Year”; LucidDB: 76.121 seconds InfoBright: 0…
Comment: Returning to InnoDB scalability
August 7, 2006 By 42 Comments
…:56 [Note] /opt/mysql/bin/mysqld: ready for connections. Version: ‘5.0.22-log’ socket: ‘/tmp/mysql.sock’ port: 3306 Source distribution… 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78…:32 [Note] /opt/mysql/bin/mysqld: ready for connections. Version: ‘5.0.22-log’ socket: ‘/tmp/mysql.sock’ port: 3306 Source distribution ==========================================================
Comment: What is stored InnoDB buffer pool
September 29, 2008 By 8 Comments
Nils, It is only for 5.0.67, will release for 5.0.68 later
Post: Air traffic queries in MyISAM and Tokutek (TokuDB)
November 5, 2009 By 26 Comments
… (SELECT carrier,count(*) as totalflights,sum(if(depdelay>10,1,0)) as ndelayed from ontime where year=2007 group by carrier…)119.5484.64 Q969.0547.67 For reference I used 5.1.36-Tokutek-2.1.0 for both MyISAM and TokuDB tests…
Comment: How to recover a single InnoDB table from a Full Backup
March 22, 2012 By 10 Comments
…57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78…99 100 done. 120323 4:38:52 InnoDB: Error: page 0 log sequence number 6094071743825 InnoDB: is in the future! …log files. See InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html InnoDB: for more information.
Post: How innodb_open_files affects performance
November 18, 2009 By 4 Comments
… be a huge waste of space. I used MySQL 5.4.2 for tests which should be as good … recovery: 091118 18:47:44 InnoDB: Warning: too many (67) files stay open while the maximum InnoDB: allowed value … fil_sys open file LRU len 0 091118 18:47:44 InnoDB: Warning: too many (68) files stay open while the …
