RE: Has MySQL just knowingly released a complete pile-of-shite??? - Nick Gaugler - com.mysql.lists.bugs

12 messages in com.mysql.lists.bugsRE: Has MySQL just knowingly released...

From	Sent On	Attachments
Paul Coldrey	23 Jul 2003 00:27
Lenz Grimmer	23 Jul 2003 04:55	.patch
Tobias Lind	23 Jul 2003 05:34
Paul Coldrey	23 Jul 2003 06:44
Sergei Golubchik	23 Jul 2003 07:38
Jeremy Zawodny	23 Jul 2003 11:55
Cory Patterson	23 Jul 2003 12:50
Paul Coldrey	23 Jul 2003 16:06
Nick Gaugler	23 Jul 2003 23:19
Vidar	24 Jul 2003 01:20
Cory Patterson	24 Jul 2003 06:58
Sergei Golubchik	25 Jul 2003 01:27

Subject:	RE: Has MySQL just knowingly released a complete pile-of-shite???
From:	Nick Gaugler (ngau...@ngworld.net)
Date:	07/23/2003 11:19:33 PM
List:	com.mysql.lists.bugs

What patches did you apply? A friend and I have been debating this issue and are trying to find which patches were applied and we've come up with two possiblities (none were listed on bugs.mysql.com, that one does not refer back to the original bug)

http://mysql.bkbits.net:8080/mysql-4.0/patch@1.1516.2.1?nav=index.html|C hangeSet@-3w|cset@1.1516.2.1 http://mysql.bkbits.net:8080/mysql-4.0/patch@1.1535?nav=index.html|Chang eSet@-3w|cset@1.1535

Has anyone else been able to reproduce this being problematic with regular queries beyond ALTER? I can understand there are some people that are running 4.0.x and say it runs fine, but if they have been running the same 4.0.x source that is less efficient they may not know any different, whereas someone that's using a fast version and then goes a slow version will easily see the problems. I may get the guts to upgrade my server to 4.0.14 and see how things go, if so I will report back. Although I am very hesitant when my two separate servers do 700 queries/sec (9.4 read/write) and 1800 queries/sec (12.6 read/write)

Nickg

-----Original Message----- From: Cory Patterson [mailto:patt...@z1g.com] Sent: Wednesday, July 23, 2003 2:51 PM To: bu...@lists.mysql.com Subject: Re: Has MySQL just knowingly released a complete pile-of-shite???

Just to add my 2 cents to this discussion.....

I have been racking my brain lately trying to figure out why the load on my database server has gone up so much since upgrading to the 4.0.12 release from 3.23. I didn't notice it right after the upgrade, but over time it has become a real issue. The load average on my server has been around 2.5 at slow times and jumps to around 8 or so during heavy use. This is a 4 processor machine with 8GB of RAM. We have been writing quite a few new applications and we have been trying to find out what was causing so many slow queries. Our assumption was bad code on our end.

After seeing this, I applied the patch to the 4.0.14 release and compiled it and now everything is running wonderfully. Load average is back down to about 0.5 and 2.0 under heavy use. Queries are lightning fast again.

I know people might say it was something else (compiler, libraries, whatever) but I know it works now and in my opinion it didn't before.

By the way, I have been using MySQL for 3 years now and I would never consider running anything else. I love the product, it is one of the few things that I never have to worry about, it always just works. But this is more than a minor bug in my opinion. If i am reading this right, this has the most effect on heavily loaded servers. We were very excited to see 4.0 become production because of replication. I think a lot of the users who fall into this category were waiting to upgrade to 4.0 because of replication and improved searching. It is just discouraging when you move 1 step forward but 2 back.

I think this should have been given a higher priority than it did, especially in a production release.

Thank you for the great product.