If you're like me, you're probably looking for the code samples almost immediately. I spitballed a different approach to it, but at the moment I believe it will be unlikely to get adopted. So it is available to all, and he welcomes the feedback - see this thread on the nginx mailing list.ĭue to limitations in the FastCGI protocol, you have to pass all the parameters you want as a single string, separated by "\n" - it's not the cleanest looking configuration, but that's how it is for now. This is cool, and I wasn't sure it actually got in a build or not, I remember it was mentioned or discussed, but sure enough, Jérôme coded it and got it in to FPM in core. It's not user-override-able, but things like htscanner or newer PHP 5.3 features could address some of that. This bridges some of the desire to have "php_value" and "php_admin_value" from Apache available. Someone in #mysql recommended I look at XtraBackup, but it seemed like too much to learn and attempt my first run at it while I was having to do a production migration.Ī little known feature in PHP-FPM 5.3.3+ (since it was integrated into PHP core) is that you can actually define PHP INI parameters inside of your nginx configuration. I think this will save my bacon, I wish I had done this sooner and not wasted that two hours originally. Without these tweaks, at 12 minutes it was at 4.5gb out of 13gb.Without these tweaks, at 107 minutes it was only at 2.2gb out of 13gb.The results are not very scientific, but here's how it breaks down so far (still in the middle of the process) I don't need any commits until the end, this is a fresh import. I also put "SET AUTOCOMMIT=0 " at the top of the script, and "COMMIT " at the bottom of the script.This server isn't used yet, so that's safe. On the destination, I set innodb_flush_log_at_trx_commit to "0" in my.cnf for the time being.On the source, I used mysqldump -opt (it seemed to dump the database faster too).Well, duh! While I was at it, I also tweaked a couple other things. If you read the documentation/blogs, it says to use -opt when running mysqldump for faster imports.
#CHANGE PASSWORD IN MOZYHOME CONFIGURATION FULL#
For one, I used -skip-opt and made my mysqldump files full INSERT statements (for verbosity and the ability to "diff" them if I ever needed to) - this was stolen from a backup script I wrote. There's a couple easy tweaks I did not use. I didn't do the math, but it would have probably taken over 10-15 hours to restore the database from the mysqldump. Great, I figured import would take longer, but not as long as it actually was originally. That's not an extremely large or complex database, however, when I ran the export script, it only took a couple minutes. I want to share this with the world, as it may have been helpful up front for me. I had to move a database that is 13gb on the filesystem (not including the shared ibdata file) - the database is a mixture of MyISAM and InnoDB tables.
0 kommentar(er)
