Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • in reply to: #28115
    christo
    Member

    Hi Peter

    Many thanks for your feedback.

    When you talk about tests that you've done: Are they the ones done by Navya ?

    I will ask to my customer if it is possible to open a connection to his server for your tests.

    Regards

    Christophe

    in reply to: #28113
    christo
    Member

    Hi everyone

    As you can see in my previous test:

    – CSV export of 200 000 rows is about 1mn if SqlYog is installed on a windows 32bits server (XP), with mysql on the same machine (32bits) or on a remote server (64bits)

    but the time becomes 18mn if SqlYog is on the 64bits server (with local D:cool:.

    and the time increases to many hours if you try to export few millions of rows.

    I confirm that export with “select .. to outfile” is about few seconds.

    The 64bits server is a windows 2008 with SAS disks and xeon CPU, and 12Go RAM (dell)

    So, my remarks are:

    – first, I have a big difference with Sqlyog on 32 or 64 bits

    – and why there is a so big difference between “CSV export” with SqlYog and the mysql command “select .. to outfile” ==> why SqlYog doesn't use this mysql command “select .. to outfile” to do the CVS export ?

    My business user likes SqlYog for the QueryBuilder and the possibility to export data in “one click”. But, he can't wait many hours during a export. He has to do his job.

    Last remark: With Wine (which 32bits) on fedora 9 64bits, the export is also very slow.

    Christo

    in reply to: SQLyog For Linux #15995
    christo
    Member

    Hi,

    I've test SqlYog on linux (fedora 9) with wine, it works.

    but a native linux version would be great.

    When ??

    Christophe

    in reply to: #28106
    christo
    Member

    Hello

    The problem is about CSV export (for example by clicking on the icon “export as” in the “Result” area of the Query pane.

    I've done some tests with Local and Remote access, with 32 an 64 bits windows.

    The test is to export 200 000 rows as result of a query.

    – Local DB : SqlYog on a 32 bits Window XP server, with local Mysql 5.1 : approx. 1mn

    – Remote DB : SqlYog on a 32 bits Window XP server, with remote Mysql 5.1 on Windows 2008 server 64bits : approx. 1mn 05sec

    – Local DB : SqlYog on Windows 2008 server 64bits, with local Mysql 5.1 : approx. 18mn

    During the first 30s, the export is fast (approx. 1500 rows/s), but the speed decreases very quickly (after 1mn is onfly 100 rows/s) !!

    – with select * from my_table limit 200000 into outfile 'd:/tmp/test.csv' : less than 1s

    So the problem concerns the use of CSV export with SqlYog on 64bits architecture : from 1mn (32bits) to 18mn (64bits).

    I've done test with version 7.13 and 7.15

    My customer is a registered user of SqlYog so I would like to find a solution for him.

    Remark: With Linux and Wine : Mysql on Fédora 9 and SqlYog with Wine (on the same server) : 27mn !!!

    PS : In a future release, it would great to have an “export as” option that use the “select … into outfile …” of mysql. It should be possible, isn't it ?

    Christophe

    in reply to: #28104
    christo
    Member

    Thank for your feedback Peter,

    I suppose that my user does queries that return more than 1 million of rows.

    As technical user, for example I will use script that create temporary table to store the data of my query , and then I will export by “Select … into outfile …”.

    But for this user, the power of sqlyog is to be able to use “QueryBuilder” and then to export to CSV file just by “clicking” : So, not technical knowledge (SQL coding) is necessary.

    So, I suspect some memory problem when sqlyog has to collect all the data returned by the query (but the server has a memory of 12Go !), since all the data has to be collected before to be exported as CSV.

    In the case of “Select … into outfile …”, mysql writes data as soon as data are returned by the query. So, not all “1 million of rows” has to be stored in memory.

    So, would it be possible with the “QueryBuilder” to make query that create table ? (like “create table as select ….)

    So, I have to make different tests with the same query and the same data :

    – windows XP 32bits, sqlyog on the same server as mysql

    – windows 2008 server 64bits, sqlyog on the same server as mysql

    – windows 2008 server 64bits for mysql , but sqlyog on a different server (XP 32bits)

    – linux server 64bits (fedora 9) for mysql, and with sqlyog and wine on this server

    Have a happy new year,

    Regards

    Christophe

    in reply to: #28102
    christo
    Member

    Hi Peter

    Thank for your reply.

    In fact, I bought SqlYog for a custumer and install this soft on his server (only 1 user).

    The first install was on XP 32bits.

    Then, he bought a new server and I migrated the mysql database on this server. Also, SqlYog had been reinstall on this new server (dell xeon, windows 2008 64 bits, SAS disks).

    So, it's a local database and exports are done on local disks.

    I have done export directly with mysql (select … into outfile …) via mysql-query tool: The export had been done in few minutes.

    With Sqlyog, CSV export of the table was not finished after 1 day.

    I will go back with more precise information later (I have to do my own tests on this server, since for the moment I have only the feedback of my customer).

    So, my initial question was about your experience on Windows 64bits with sqlyog

    Regards

Viewing 6 posts - 1 through 6 (of 6 total)