8.0: Excessive memory usage during mysqldump
Posted by:
John Adams
Date: February 27, 2023 11:31AM
Hi, folks,
I ran the first mysqldump against a database with a physical size of 83GB on a server with 16GB of memory. I hit 99% memory utilization and used .5GB of swap. That seems excessive to me, but maybe I'm wrong. These are the options I was using: --flush-logs --lock-tables=false --single-transaction --quick
The innodb_buffer_pool_size is 3GB and there are three instances.
What can I do to reduce memory utilization? I don't want to throw memory at this just to keep notifications from pinging me in the middle of the night.
Thanks,
John A
----------------------
BUFFER POOL AND MEMORY
----------------------
Total large memory allocated 0
Dictionary memory allocated 20975811
Buffer pool size 196590
Free buffers 3063
Database pages 193262
Old database pages 71285
Modified db pages 0
Pending reads 0
Pending writes: LRU 0, flush list 0, single page 0
Pages made young 5225, not young 23297159
0.00 youngs/s, 0.00 non-youngs/s
Pages read 3569013, created 535, written 7657
0.00 reads/s, 0.00 creates/s, 0.00 writes/s
No buffer pool page gets since the last printout
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
LRU len: 193262, unzip_LRU len: 0
I/O sum[0]:cur[0], unzip sum[0]:cur[0]