I have a SQL DB that I export to a local MySQL instance on my development machine regularly. The export starts out screaming fast but as it progresses the processes slows to a crawl.
This is not caused by larger tables later in the update because if I shut down and restart HeidiSQL and start the export at a large table it's fast again.
For now I am resorting to doing several exports selecting just a few tables at a time but this "feels" like a bug to me, perhaps a memory leak? Monitoring HeidiSQL's memory usage during an export the usage bounces all over but get's quite high (up to 2GB at times).
I've tried adjusting the export settings, changing the max insert size up and down, and nothing seems to improve the performance degradation.
This issue shows up regardless of the source and destination servers. I have three servers on my local network (one screaming 16-core, 32GB, SSD) but the issue shows up with all of them.
Has anyone else encountered this?