Bug #86143 Exporting rows to .csv taking much longer than expected
Submitted: 1 May 2017 0:47 Modified: 2 May 2017 7:29
Reporter: Theresa Lemak Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:6.3.9 OS:Windows
Assigned to: CPU Architecture:Any
Tags: regression

[1 May 2017 0:47] Theresa Lemak 
Description:
I'm exporting 400,000, to 500,000 rows at a time to .csv. Previous versions of workbench handled the job in <10 seconds. After updating to 6.3.9 the export takes ~10 minutes a job. The amount of memory usage has also increased significantly since the previous version. 

How to repeat:
Attempt to export 400,000 rows of data to .csv. View the RAM and CPU usage differences between Workbench 6.3.9 and 6.3.8 (or older)

Suggested fix:
Review the previous version(s) and correct any changes that impacted this feature.
[2 May 2017 7:29] MySQL Verification Team 
Hello Theresa Lemak,

Thank you for the report and feedback.
Verified as described with WB 6.3.9 on Win7.

Thanks,
Umesh
[28 Jun 2018 6:58] Chiranjeevi Battula 
http://bugs.mysql.com/bug.php?id=91426 marked as duplicate of this one.
[22 Mar 2023 1:28] Wang Shiyao 
This issue still exists in 8.0.x.
I have a table of 1 Million rows.
Exporting this table to json format only takes several seconds to complete.
However, if I export this table to csv format, it took me more than 24 hours to complete.
In the above example, I selected only one column to export.