That's a good way to get a corrupt export unless you shut down the server first.
-Jonathan On Mon, Dec 29, 2008 at 5:18 PM, William Attwood <wattw...@gmail.com> wrote: > You may also try just tarballing the entire data folder for MySQL; may be > faster if you have that much data to export. > -Will > > On Mon, Dec 29, 2008 at 4:11 PM, William Attwood <wattw...@gmail.com> wrote: > >> Hmmm. You can set the MySQLDump memory usage in your MySQL Configuration >> file. [mysqldump] >> quick >> max_allowed_packet = 16M >> >> >> That should help with the processor load spike, hopefully. >> >> -Will >> >> >> On Mon, Dec 29, 2008 at 4:06 PM, Ryan Byrd <ryanb...@gmail.com> wrote: >> >>> So, let's say there is this centos box is running a mysql database >>> that has db tables that are pretty big, (some > 1x10^6 rows) >>> >>> and when one runs mysqldump on the database, it spikes the load >>> average, as reported by top, on the box to about 15 >>> >>> this box also is running apache >>> >>> when the load average spikes to 10, apache pages are SLOW to load. >>> >>> how can one throttle the mysqldump so it doesn't use as many system >>> resources? >>> >>> -r >>> >>> /* >>> PLUG: http://plug.org, #utah on irc.freenode.net >>> Unsubscribe: http://plug.org/mailman/options/plug >>> Don't fear the penguin. >>> */ >>> >> >> > > /* > PLUG: http://plug.org, #utah on irc.freenode.net > Unsubscribe: http://plug.org/mailman/options/plug > Don't fear the penguin. > */ > /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
