On Tue, 2 May 2006, Christoph Haas wrote:
By way of comparison my systems were thrashing badly even with 2Gb of ram
because mySQL wasn't using enough memory. Allowing it to grow to 1Gb ram
solved it almost entirely.
I just have 512 MB of RAM but you made me think about my server parameters.
On Wed, May 03, 2006 at 11:02:20AM +0100, Alan Brown wrote:
On Tue, 2 May 2006, Christoph Haas wrote:
While I used settings from the large my.cnf example configuration file
and had a slight speedup it still took longer than a few hours so I
interrupted.
What indexes do you have?
PRIMARY
On Wed, 3 May 2006, Christoph Haas wrote:
That won't help, but proper indexing should speed things up.
Au contraire. In this case the indexing is slowing down the import.
Importing the pure data is taking a few minutes only while creating the
indexes is taking a day.
Doh, of course...
Are
On Wed, May 03, 2006 at 12:10:38PM +0100, Alan Brown wrote:
On Wed, 3 May 2006, Christoph Haas wrote:
That won't help, but proper indexing should speed things up.
Au contraire. In this case the indexing is slowing down the import.
Importing the pure data is taking a few minutes only while
On Mon, May 01, 2006 at 10:43:11PM +0100, Alan Brown wrote:
On Mon, 1 May 2006, John Kodis wrote:
You have more CPU than I do, but only about half the memory. Since
you say that the disks are thrashing, I'd guess that the lack of
memory is more likely to be the culprit than the difference
Evening,
I'm using MySQL (4.1) as an index storage with the default MyISAM table
format. Unfortunately the partition holding the MySQL databases ran full
and the database became corrupt. So I wanted to restore the mysqldump of
the index from the day before.
Now it's 12 hours after I started to
On Mon, 1 May 2006 12:04:10 +0200
Christoph Haas [EMAIL PROTECTED] wrote:
Evening,
I'm using MySQL (4.1) as an index storage with the default MyISAM table
format. Unfortunately the partition holding the MySQL databases ran full
and the database became corrupt. So I wanted to restore the
On Mon, May 01, 2006 at 12:04:10PM +0200, Christoph Haas wrote:
Now it's 12 hours after I started to restore the 2.4 GB dump file
and MySQL still seems to be doing the /*!4 ALTER TABLE `File`
ENABLE KEYS */ part of the dump. The disk is trashing like fury
while the database is creating
