Dumping large MySQL database

Thu, 02 Jun 2016 00:00:00 +0000

Problem

Not going into details of credentials basic mysqldump command looks like this:

mysqldump database > database_dump.sql

Dump file size was ~3GB which might take quite long. Especially when the connection to mysql server was not fast enough.

Solution

After a few attempts and noticing that it might take too long to fetch all data I found out that there is a nice switch in mysql and mysqldump commands.

--compress, -C

Switch will tell mysql server to compress the dump on the fly so you can save a lot of bandwidth. However both sides needs to support the setting. Note that you may also use that switch with mysql command.

Log Levels Performance

Sat, 14 May 2016 00:00:00 +0000

Problem

Take an example with grails log.debug() call. Let’s say I want to log a very often executed code.

Long sum = 0
(1..1000).each { number ->
 ++sum
 log.debug "Sum = ${sum}"
}

I use log.debug so my information is logged only if my project configuration allows that. That way if we turn off DEBUG, the logged line should not affect application speed. But is that really true?

Let’s check if the logged value is really not accessed? To do so we need to turn off DEBUG and modify the code:

Performance on Bitecode blog

Dumping large MySQL database

Problem

Solution

Log Levels Performance

Problem