16 messages in com.mysql.lists.win32Re: MySQL 3.23.56 slow on win32?
FromSent OnAttachments
Jon Martin Solaas21 Apr 2004 08:10 
Petr Vileta21 Apr 2004 15:26 
Jon Martin Solaas21 Apr 2004 15:42 
Randy Clamons21 Apr 2004 16:35 
Jon Martin Solaas21 Apr 2004 16:49 
Petr Vileta21 Apr 2004 16:53 
Jon Martin Solaas21 Apr 2004 17:07 
Randy Clamons21 Apr 2004 17:33 
Petr Vileta21 Apr 2004 19:49 
Raúl D. Pittí Palma21 Apr 2004 21:13 
Raul pitti21 Apr 2004 21:37 
Jon Martin Solaas22 Apr 2004 01:09 
Jon Martin Solaas22 Apr 2004 01:14 
Jon Martin Solaas22 Apr 2004 01:18 
Mike M Brando22 Apr 2004 10:23 
Jon Martin Solaas22 Apr 2004 22:34 
Subject:Re: MySQL 3.23.56 slow on win32?
From:Randy Clamons (ran@novaspace.com)
Date:04/21/2004 04:35:14 PM
List:com.mysql.lists.win32

Jon,

Look in you mysql folder. You will find 4 sample configuration files. They have an extension cnf, so they will have a file type SpeedDial, and no extension displays. The names are my-small, my-medium, my-large, my-huge.
I remember the initial setup to be most like my-small.

Open one with a text editor (Notepad) and you can see what variables can be set to tweek your setup and an idea of what those values might be.

You should find c:\my.cnf. You will also find c:\WINNT\my.ini. Both files are
used if both are found. It reads my.ini first, then my.cnf. Anything in my.cnf
will override anything in my.ini. It's recommended that you delete my.cnf on windows machines to keep things simple.

When you do the import, it saves time to create indexes after the tables have
been built. mysqldump will create a script that does not work this way. Since
you already have tables defined, it might be better to TRUNCATE your tables,
drop all indexes, use LOAD DATA INFILE to load the tables, then add all indexes
back. To export the data from your live db, look for "INTO OUTFILE" in mySql
docs.

------------Original Message------------ From: Jon Martin Solaas <jon.@objectlabs.no> To: win@lists.mysql.com Date: Wed, Apr-21-2004 3:48 PM Subject: Re: MySQL 3.23.56 slow on win32?

Thanks, this is useful, but still it doesn't answer my question, why is MySQL so slow on Windows, and it doesn't run my massage script either, which is written in php, by the way...

Importing the dump on my P4 3.06 GHz Linux machine took under one minute today, as opposed to many hours (and still not finished) on a WinXP P4 1.8 GHz.

EWeek had a benchmark some time ago, testing several databases (and jdbc-drivers) on Win32, MySQL was about as fast as Oracle, so clearly MySQL will perform well on Win32 given certain conditions I obviously don't know about ...

On Thu, 2004-04-22 at 00:27, Petr Vileta wrote:

I have a medium size database (15-20 tables, a couple of thousands rows in some, less in others).

The database is a questionairie/web survey, so on a semi-daily basis I dump it with mydsqldump from the Linux server, and then import on a Win32 machine (P4 ~2MHz), for execution of an analyzis script. Importing takes «long time», and running the massage-script preparing data for SPSS takes just too long (doesn't run on one night).

It might well be that my script could be optimized, and the database de-normalized a little, but anyhow, doing the same job on my old Linux laptop (400Mhz) takes only hours, not days ...

You can to take BACKUP TABLE table1,table2...TO ...; on Linux and DROP TABLE table1; DROP TABLE table2; ... RESTORE TABLE table1 FROM ...; RESTORE TABLE table2 FROM ...; on Windows. Files transfer from Linux to Windows do as a binary and case sensitive. Is sufficient to transfer *.MYD and *.frm files only from backup directory.