--0-228028267-1311007212=:66004
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

[Process:]=0A=C2=A0=0AImporting=0Adelimited text files from a Windows based=
server to a MySQL 5.1.41 instance=0A(multiple databases) on a single Ubunt=
u 10.04.2 host. =0A=C2=A0The=0Aprocess is initiated on the Windows server v=
ia the MySQL exe using =E2=80=98load data=0Alocal infile=E2=80=99.=0AThere =
are=0A20 databases total and we import 15 files per database =E2=80=93 1 fi=
le per=0Atable.=C2=A0 =0AAll tables=0Ause the MyISAM engine.=0APrior to=0Ae=
ach import, we truncate the destination tables.=0AAll=0Aprocessing is done =
sequentially.=0A=C2=A0=0A[Issues:]=0A=C2=A0=0AThe process=0Awill run fine f=
or about 2 weeks then continues to increase significantly in=0Aoverall proc=
essing time.=C2=A0 For example, we=E2=80=99ll see a 35 minute run-time for=
=0A2 weeks, then the next day its 55 minutes, then 80 minutes, etc, then wi=
thout=0Aany changes, it will drop back to 35 after about a week (length of =
times=0Avary.)=C2=A0 It does not seem to be the result of any other process=
ing=0Arequirements as the server is basically dedicated to MySQL only and t=
here are=0Ano manually added CRON tasks.=0AEven the=0Atruncate table steps =
appear to be affected.=0A=C2=A0=0AAn=0Acomparison of =E2=80=98show status=
=E2=80=99 on a normal day vs a slow day does not appear to=0Ashow any major=
issues other than a high volume of aborted_connects but this variable=0Ase=
ems to increase regularly, outside of the actual import processing window.=
=0A=C2=A0=0ANot sure if=0Athis is some sort of MySQL resource buildup or so=
mething related to the OS.=0A=C2=A0=0AAny input=0Awould be greatly apprecia=
ted.
--0-228028267-1311007212=:66004--

maybe its is obvoius but

did you look at the statistics ?
did you try "optimize table" ?

re,
wh

Am 18.07.2011 18:40, schrieb A F:
> [Process:]
>
> Importing
> delimited text files from a Windows based server to a MySQL 5.1.41 instance
> (multiple databases) on a single Ubuntu 10.04.2 host.
> The
> process is initiated on the Windows server via the MySQL exe using ‘load data
> local infile’.
> There are
> 20 databases total and we import 15 files per database – 1 file per
> table.
> All tables
> use the MyISAM engine.
> Prior to
> each import, we truncate the destination tables.
> All
> processing is done sequentially.
>
> [Issues:]
>
> The process
> will run fine for about 2 weeks then continues to increase significantly in
> overall processing time. For example, we’ll see a 35 minute run-time for
> 2 weeks, then the next day its 55 minutes, then 80 minutes, etc, then without
> any changes, it will drop back to 35 after about a week (length of times
> vary.) It does not seem to be the result of any other processing
> requirements as the server is basically dedicated to MySQL only and there are
> no manually added CRON tasks.
> Even the
> truncate table steps appear to be affected.
>
> An
> comparison of ‘show status’ on a normal day vs a slow day does not appear to
> show any major issues other than a high volume of aborted_connects but this variable
> seems to increase regularly, outside of the actual import processing window.
>
> Not sure if
> this is some sort of MySQL resource buildup or something related to the OS.
>
> Any input
> would be greatly appreciated.

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2 [at] m.gmane.org