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 it was my fault so I decided not to report it until I did some further research. -M On Mon, Jun 24, 2002 at 11:52:47AM -0700, Steven Roussey wrote: > I tried 'skip-name-resolve' but it had no impact. :( So it may have > nothing to do with name resolution. > > Here are the results in file RUN-mysql-Linux_2.4.16_0.13smp_i686: > > > I'm going to run the tests on .47 next 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 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 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 to connect, causing 0.5 to 1.0 > second > > >> delay on connection. Using persistent connections from PHP does not > > make > > >> much of a difference. I thought it might be the hostname lookup > changes > > >> so I chose skip-grant-tables. This doesn't actually skip the > hostname > > >> lookup though and had no effect. > > >> > > >> Most queries are shorter than 1 second so this problem causes > > >> catastrophic problems by making queries last a multiple times > longer, > > >> which make the number of concurrent queries jump exponentially. > This is > > >> a bad thing. And sadly makes 3.23.51 unusable. > > >> > > >> Does anyone else note these types of issues? > > > > Jeremy> As another data point for you, I've got 3.23.51 running on our > > master > > Jeremy> quite well. The difference is that I built it from source (to > get > > a > > Jeremy> critical InnoDB patch). I don't recall which compiler the > MySQL > > folks > > Jeremy> used (and which glibc), but my source build used Debian > Woody's > > gcc > > Jeremy> 2.95.4. > > > > We are using gcc 2.95.3 and a patched glibc, the later one that we > > used in many builds before. > > > > This is the first email I got that 3.23.51 would be slow. > > > > Steven, could you try to run the MySQL benchmark suite on your machine > > and post me the results ? > > > > cd sql-bench > > perl run-all-tests --log > > > > The file I am interested in is the summary file named 'output/RUN-*' > > > > Regards, > > Monty > > > > --------------------------------------------------------------------- > Before posting, please check: > http://www.mysql.com/manual.php (the manual) > http://lists.mysql.com/ (the list archive) > > To request this thread, e-mail <[EMAIL PROTECTED]> > To unsubscribe, e-mail <[EMAIL PROTECTED]> > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > -- Michael Bacarella | Netgraft Corporation | 545 Eighth Ave #401 Systems Analysis | New York, NY 10018 Technical Support | 212 946-1038 | 917 670-6982 Managed Services | [EMAIL PROTECTED] --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
