| | 10 | * MOPS processing czar |
| | 11 | * I'm still fighting with mysql-5.1 on ippc00 |
| | 12 | * Note: mysql-5.5 is not a development version but the stable version. 5.1 is already considered outdated by mysql.com. The latest GA version is precisely MySQL Community Server 5.5.8. |
| | 13 | * I successfully installed it from source and make it run. The configuration is a real pain. For info, the "right" call to {{{configure}}} is: |
| | 14 | {{{ |
| | 15 | ./configure --sysconfdir=/etc/mysql --localstatedir=/var/lib/mysql --enable-profiling --enable-local-infile |
| | 16 | --with-mysqld-user=mysql --with-big-tables --with-plugins=partition,innodb_plugin,innobase |
| | 17 | --enable-thread-safe-client --with-unix-socket-path=/var/run/mysql/mysql.sock |
| | 18 | }}} |
| | 19 | Note that it is installed in /usr/local (I tried with --prefix=/usr) |
| | 20 | * To make comparisons, I ingested a nebulous dump (from mysql-neb-ippdb00-2011-01-07T00:30:05.dump.gz). Ingestion took about 38 hours! |
| | 21 | * I ran OPTIMIZE TABLE on each of the table. Some results:[[BR]] |
| | 22 | OPTIMIZE TABLE directory -> 29.84 sec / 4409811 entries [[BR]] |
| | 23 | OPTIMIZE TABLE instance -> 4 hours 44 min 42.60 sec / 367254059 entries [[BR]] |
| | 24 | OPTIMIZE TABLE storage_object -> 3 days 7 hours 15 min 53.60 sec / 332149048 entries [[BR]] |
| | 25 | I was running another ingestion process of the same dump when storage_object was optimized. This might explain why it took longer but I don't understand why it took so long (I would have accepted a total of 38 hours + 5 hours (4h44 with a similar table in size)). |
| | 26 | * I'm working now on representative nebulous SQL statements to see if optimize changed anything. I'm also about to partition the tables. |
