This is prototype for multi-process Optimized Upgrade Replay from Magento 1.5 (1.10 EE) and lower to 1.6 (1.11 EE) and higher. In order to run optimized replay you need to run original upgrade in database with same structure. Replay script uses pdo_mysql.log to read queries and estimate execution time.
Disk may become bottleneck during upgrade replay.
- Was not tested with table prefixes
- THIS IS PROTOTTYPE. Please make sure it works before running in production.
Real life results
- 1.9 EE -> 1.11 EE ==> Original upgrade ~34 hours vs Optimized Replay 4 hours
- 1.4 CE -> 1.12 EE ==> Original upgrade ~15 hours vs Optimized Replay 2 hours
- PHP 5.2+
- POSIX extension
- Magento 1.6+ (1.11 EE) to upgrade to
Prepare Varien_Db_Adapter_Pdo_Mysql in Magento 1.6+ Enable debug mode:
//protected $_debug = false; // Original protected $_debug = true;
Log all queries:
// protected $_logAllQueries = false; // Original protected $_logAllQueries = true;
Steps to upgrade
- Trigger upgrade and wait until it ends.
- Copy var/debug/pdo_mysql.log from upgraded Magento to shell direcory of new copy.
- Copy upgrade_replay.php and shell directory of new copy.
- cd [new copy]/shell && php -f upgrade_replay.php
Create posix FIFO for inter-process communications. Start multiple php processes using proc_open(). Prepare queries for execution:
- Strip out duplicate queries.
- Merge similar ALTER TABLE queries.
- Optimize one data-specific query
- Split in chunks for parallel execution. Child processes are waiting for data in STDIN and puting their IDs in fifo once process is finished. Parent process reads fifo in blocking mode. Once Parent gets ID of child, it sends next query or waits till othe queries from chunk will be executed. Data upgrades are triggered the same way as in original.
Debug function to make shure that parsing FSM works fine.
Triggering upgrade in multiple threads ('true' will really trigger upgrade).
// public function run($threads, $real = false) //$track->run(4); $track->run(12, true);