Foreign key processing is suspected to cause performance bottleneck.
One test manifesting this is to load employee database from: https://launchpad.net/test-db/, and measure load times when FKs are enabled / disabled.
Here are test results with MySQL 5.6.17 development head version, compared to native MySQL 5.6.17:
mysql -uroot < employees.sql
2 node GC cluster 5.6.17 dev mysql 5.6.17
FK ON: 1m32.696s 0m36.379s FK OFF: 1m1.442s 0m35.025s
=> FK overhead in cluster is roughly 50%
Foreign key processing is suspected to cause performance bottleneck.
One test manifesting this is to load employee database from: https:/ /launchpad. net/test- db/, and measure load times when FKs are enabled / disabled.
Here are test results with MySQL 5.6.17 development head version, compared to native MySQL 5.6.17:
mysql -uroot < employees.sql
FK ON: 1m32.696s 0m36.379s
FK OFF: 1m1.442s 0m35.025s
=> FK overhead in cluster is roughly 50%