Is there anything with my table DDL that would slow down an import? CREATE TABLE `some_schema`. These are far more efficient and you dont need a TVF (Table valued function) just to create a table from csv. I have reached out to their support to try and understand what command Sequel Pro is using to load data. Sequel Pro does import the data in 30 seconds, even with the key. Quickly edit with inline table editor, apply hex viewing with row editor, and export to csv, mysql, xml, or json for easy sharing. the tags table and assumed it must be the key slowing things down.
I looked at the DDL for what I had been testing with vs. The reason why I suspected it was the key is that I tried to use the same tags.csv dataset that the other commenter used, but for that table (and for the same DDL that the commenter used) there was no speed difference between DataGrip and Sequel Pro.
I tried to import the data without the key, but it still took about 2m40s via DataGrip.
Sqlpro create table from csv update#
16:03:39 finished - execution time: 2 m 50 s 437 ms, fetching time: 1 ms, total update count: 10000 INSERT INTO import_perf_test_tags_datagrip (user_id, email) VALUES (?, ?) 16:00:49 finished - execution time: 87 ms, fetching time: 106 ms, total result sets count: 1 SELECT t.* FROM import_perf_test_tags_datagrip t 16:00:48 finished - execution time: 171 ms Is it possible to see the exact command that DataGrip is using to load data so that I can cross reference against what my other SQL client is doing?Īgain, this is all I see in the DataGrip logs: I did do some testing on a table without any keys specified and there was no performance discrepancy. I have another MySQL client on my mac (Sequel Pro) that will import a 10,000 row file with two columns (IDs and email addresses) in about 30 seconds, whereas DataGrip takes almost 3 minutes. I am only experiencing performance issues with the import. Server ping isn't very straightforward to measure since I'm connecting via an SSH tunnel.
0 kommentar(er)
