12, 2002 6:17 PM
Subject: RE: Load problems with 3.23.51
Just a note: I tried MySQL 4.0.2 and it works fine. Seems to be only
3.23.51 built by MySQL itself that has the issue. Releases before, and
now a release after (albeit a 4.0.x version) work fine.
Sincerely,
Steven Roussey
http
12, 2002 6:17 PM
Subject: RE: Load problems with 3.23.51
Just a note: I tried MySQL 4.0.2 and it works fine. Seems to be only
3.23.51 built by MySQL itself that has the issue. Releases before, and
now a release after (albeit a 4.0.x version) work fine.
Sincerely,
Steven Roussey
http
David,
Tuesday, July 16, 2002, 3:55:46 PM, you wrote:
DB Same thing here, mysql 3.23.51 works well during about 2 hours then
DB suddently load average grow up to 200 and more ...
DB Load average is less than 4 with 3.23.49.
DB We're using binary tar.gz non max versions from Mysql.com
DB OS :
Just a note: I tried MySQL 4.0.2 and it works fine. Seems to be only
3.23.51 built by MySQL itself that has the issue. Releases before, and
now a release after (albeit a 4.0.x version) work fine.
Sincerely,
Steven Roussey
http://Network54.com/?pp=e
I have MySQL 3.23.47 running on our sever.
Just an update: I installed a new fresh version of RedHat 7.3 (smp
Athlon) and a new copy of MySQL 3.23.51, but the problem remains.
Sincerely,
Steven Roussey
http://Network54.com/?pp=e
-
Before posting, please check:
On Sat, Jun 29, 2002 at 10:47:47PM -0700, Steven Roussey wrote:
Tomorrow I'll try doing my own compile with gcc3.1. Note the other
guy that had the same problem that went away after he compiled it
himself:
Even gcc 2.95.3 or .4 will work well based on what I've seen. We can
still sustain
To: Steven Roussey
Subject: Re: Load problems with 3.23.51
Can you humor me and try running the command:
ps -eo pid,tt,user,fname,tmout,f,wchan
on that system a few times? Mine was far too hosed for this command
to ever get off the ground. I think that'd help determine
if there's
Hi!
Steven == Steven Roussey [EMAIL PROTECTED] writes:
Steven I tried the skip-name-resolve and it had no effect. So there goes my
Steven hypothesis.
Steven Here are the results from test:
Steven Benchmark DBD suite: 2.14
Steven Date of test:2002-06-24 11:19:19
Steven Running tests
Another option is to run the 3.23.51 server for a while and when you
get a load problem do 'mysqladmin proc ext'. This command should show
us if MySQL is using more table scans than usual.
The load problem shows up immediately.
+--++
| Variable_name
, 2002 2:55 AM
Subject: Re: Load problems with 3.23.51
On Sat, Jun 22, 2002 at 05:25:59PM -0700, Steven Roussey wrote:
Hi all,
I have MySQL 3.23.47 running on our sever. I skipped 48 through 50 and
tried 51. No dice. It does not handle load, CPU and the load average go
through the roof
Hi!
Jeremy == Jeremy Zawodny [EMAIL PROTECTED] writes:
Jeremy On Sat, Jun 22, 2002 at 05:25:59PM -0700, Steven Roussey wrote:
Hi all,
I have MySQL 3.23.47 running on our sever. I skipped 48 through 50 and
tried 51. No dice. It does not handle load, CPU and the load average go
through
Jeremy Zawodny writes:
On Sat, Jun 22, 2002 at 05:25:59PM -0700, Steven Roussey wrote:
As another data point for you, I've got 3.23.51 running on our master
quite well. The difference is that I built it from source (to get a
critical InnoDB patch). I don't recall which compiler the MySQL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have MySQL 3.23.47 running on our sever. I skipped 48 through 50 and
tried 51. No dice. It does not handle load, CPU and the load average go
through the roof. I'm using Red Hat Linux 7.2 and the official mysql
binaries. It appears to be slow
/?pp=e
-Original Message-
From: Michael Widenius [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 24, 2002 4:24 am
To: [EMAIL PROTECTED]
Cc: Steven Roussey; [EMAIL PROTECTED]
Subject: Re: Load problems with 3.23.51
Hi!
Jeremy == Jeremy Zawodny [EMAIL PROTECTED] writes:
Jeremy
]
Subject: Re: Load problems with 3.23.51
Hi!
Jeremy == Jeremy Zawodny [EMAIL PROTECTED] writes:
Jeremy On Sat, Jun 22, 2002 at 05:25:59PM -0700, Steven Roussey
wrote:
Hi all,
I have MySQL 3.23.47 running on our sever. I skipped 48 through 50
and
tried 51. No dice. It does not handle
to see if there is any
difference.
Sincerely,
Steven Roussey
http://Network54.com/?pp=e
-Original Message-
From: Michael Widenius [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 24, 2002 4:24 am
To: [EMAIL PROTECTED]
Cc: Steven Roussey; [EMAIL PROTECTED]
Subject: Re: Load
On Mon, Jun 24, 2002 at 03:11:53PM -0400, Michael Bacarella wrote:
I will second this.
I attempted an upgrade from 3.23.50 to 3.23.51 and hit immediate
performance problems. I tried for about 20 minutes to see what was
causing it but to no avail. I reverted to 3.23.50.
At first I thought
On Mon, Jun 24, 2002 at 12:43:47PM -0700, Jeremy Zawodny wrote:
I will second this.
I attempted an upgrade from 3.23.50 to 3.23.51 and hit immediate
performance problems. I tried for about 20 minutes to see what was
causing it but to no avail. I reverted to 3.23.50.
At first I
Sent: Monday, June 24, 2002 4:14 PM
Subject: Re: Load problems with 3.23.51
Jeremy Zawodny writes:
On Sat, Jun 22, 2002 at 05:25:59PM -0700, Steven Roussey wrote:
As another data point for you, I've got 3.23.51 running on our master
quite well. The difference is that I built it from
I used the mysql builds myself. Funny thing is that I use your tool
'mytop', which is very cool by the way, to watch things and it pauses
for about 5-8 seconds when refreshing with .51 and is almost instant
with .47
Sincerely,
Steven Roussey
http://Network54.com/?pp=e
-Original
On Sat, Jun 22, 2002 at 05:25:59PM -0700, Steven Roussey wrote:
Hi all,
I have MySQL 3.23.47 running on our sever. I skipped 48 through 50 and
tried 51. No dice. It does not handle load, CPU and the load average go
through the roof. I'm using Red Hat Linux 7.2 and the official mysql
21 matches
Mail list logo
