Comments for The data charmer http://blogs.mysql.com/gmax Wizardry and community Sat, 17 May 2008 16:23:21 +0000 http://wordpress.org/?v=2.3.2 Comment on Tutorial and session at MySQL Users Conference 2008 by Proxy Server http://blogs.mysql.com/gmax/2007/12/19/tutorial-and-session-at-mysql-users-conference-2008/#comment-94 Proxy Server Tue, 06 May 2008 05:22:29 +0000 http://blogs.mysql.com/gmax/2007/12/19/tutorial-and-session-at-mysql-users-conference-2008/#comment-94 Hello webmaster Wow what a fantastic article about Proxy Server! Your keen insight into Proxy Server is informative and creative. I look forward to reading other articles you have. Thanks. Hello webmaster Wow what a fantastic article about Proxy Server! Your keen insight into Proxy Server is informative and creative. I look forward to reading other articles you have. Thanks.

]]> Comment on db4free: Get a taste of Falcon without installing! by Pythian Group Blog http://blogs.mysql.com/gmax/2008/03/31/db4free-get-a-taste-of-falcon-without-installing/#comment-80 Pythian Group Blog Fri, 04 Apr 2008 18:21:15 +0000 http://blogs.mysql.com/gmax/2008/03/31/db4free-get-a-taste-of-falcon-without-installing/#comment-80 <strong>Log Buffer #91: a Carnival of the Vanities for DBAs...</strong> Welcome to the 91st edition of Log Buffer, the weekly review of database blogs. For a change, let’s begin with some PostgreSQL stuff. On Tending the Garden, Selena Deckelmann gives her retrospective thanks to those who attended and presented th... Log Buffer #91: a Carnival of the Vanities for DBAs…

Welcome to the 91st edition of Log Buffer, the weekly review of database blogs.
For a change, let’s begin with some PostgreSQL stuff. On Tending the Garden, Selena Deckelmann gives her retrospective thanks to those who attended and presented th…

]]> Comment on IRC session with Bob Brewin - Wed, March 12 - 9am PDT - 5pm CET by Sheeri http://blogs.mysql.com/gmax/2008/03/10/mysql-meetup-with-bob-brewin-wed-march-12-9am-pdt-5pm-cet/#comment-71 Sheeri Mon, 10 Mar 2008 16:04:17 +0000 http://blogs.mysql.com/gmax/2008/03/10/mysql-meetup-with-bob-brewin-wed-march-12-9am-pdt-5pm-cet/#comment-71 That tinyurl gives an error: "Follow these instructions: change the domain name that appears in the URL in the address bar of your web browser from tinyurl.com to b.tinyurl.com and leave everything else the same. Press the "go" button or hit the return key to be redirected to the page the TinyURL you followed goes to." and in fact <a HREF="http://b.tinyurl.com/ytnowa" rel="nofollow">http://b.tinyurl.com/ytnowa</A> works. That tinyurl gives an error:
“Follow these instructions: change the domain name that appears in the URL in the address bar of your web browser from tinyurl.com to b.tinyurl.com and leave everything else the same. Press the “go” button or hit the return key to be redirected to the page the TinyURL you followed goes to.”

and in fact

http://b.tinyurl.com/ytnowa
works.

]]> Comment on Spring cleaning in MySQL supported platforms by Xaprb http://blogs.mysql.com/gmax/2008/02/20/spring-cleaning-in-mysql-supported-platforms/#comment-68 Xaprb Wed, 20 Feb 2008 23:59:31 +0000 http://blogs.mysql.com/gmax/2008/02/20/spring-cleaning-in-mysql-supported-platforms/#comment-68 Excellent graphic. From your recent travels, I take it? Excellent graphic. From your recent travels, I take it?

]]> Comment on Introducing the 15 seconds rule by gmax http://blogs.mysql.com/gmax/2007/10/19/introducing-the-15-seconds-rule/#comment-30 gmax Fri, 21 Dec 2007 11:51:48 +0000 http://blogs.mysql.com/gmax/2007/10/19/introducing-the-15-seconds-rule/#comment-30 Apparently, you don't understand what this is about. It is not about installing MySQL as your first server, which is easy enough in any OS. It's about having *many* server instances in the same box, which is not as easy as you think. Apparently, you don’t understand what this is about.
It is not about installing MySQL as your first server, which is easy enough in any OS. It’s about having *many* server instances in the same box, which is not as easy as you think.

]]> Comment on Introducing the 15 seconds rule by Moon's father http://blogs.mysql.com/gmax/2007/10/19/introducing-the-15-seconds-rule/#comment-29 Moon's father Fri, 21 Dec 2007 11:15:10 +0000 http://blogs.mysql.com/gmax/2007/10/19/introducing-the-15-seconds-rule/#comment-29 I don't think it is useful. To install mysql is very easy, and learn it too. Users don't need to learn this again. I don’t think it is useful.
To install mysql is very easy,
and learn it too.
Users don’t need to learn this again.

]]> Comment on Falcon serendipitous performance findings by gmax http://blogs.mysql.com/gmax/2007/12/02/falcon-serendipitous-performance-findings/#comment-16 gmax Mon, 03 Dec 2007 21:12:33 +0000 http://blogs.mysql.com/gmax/2007/12/02/falcon-serendipitous-performance-findings/#comment-16 Jeremy, Jay, That was not a miscalculation, but bad grammar :). Not 176 times faster than MyISAM, but faster than MyISAM 176 times. Sorry for the mixup. Giuseppe Jeremy, Jay,
That was not a miscalculation, but bad grammar :).
Not 176 times faster than MyISAM, but faster than MyISAM 176 times.

Sorry for the mixup.

Giuseppe

]]> Comment on Falcon serendipitous performance findings by Jay Pipes http://blogs.mysql.com/gmax/2007/12/02/falcon-serendipitous-performance-findings/#comment-15 Jay Pipes Mon, 03 Dec 2007 20:57:03 +0000 http://blogs.mysql.com/gmax/2007/12/02/falcon-serendipitous-performance-findings/#comment-15 Correction on numbers.... Hi G, I detected a miscalculation in your results... 0.002847/0.000254 = 11.208661417 0.000302/0.000254 = 1.188976378 So, Falcon is approximately 11.2 times faster than MyISAM for the test and approximately 1.19 times faster than InnoDB... Not quite the awesome results you state, but still impressive. Cheers, jay Correction on numbers….

Hi G, I detected a miscalculation in your results…

0.002847/0.000254 = 11.208661417
0.000302/0.000254 = 1.188976378

So, Falcon is approximately 11.2 times faster than MyISAM for the test and approximately 1.19 times faster than InnoDB…

Not quite the awesome results you state, but still impressive.

Cheers,

jay

]]> Comment on Falcon serendipitous performance findings by Jeremy Cole http://blogs.mysql.com/gmax/2007/12/02/falcon-serendipitous-performance-findings/#comment-14 Jeremy Cole Sun, 02 Dec 2007 23:07:30 +0000 http://blogs.mysql.com/gmax/2007/12/02/falcon-serendipitous-performance-findings/#comment-14 Hi Giuseppe, Hmm, to me your comments on performance and the numbers in your table do not line up at all. Are your comments based on some other data? myisam/falcon = 11.208661 innodb/falcon = 1.188976 Where did you get your 143x and 176x numbers? Hi Giuseppe,

Hmm, to me your comments on performance and the numbers in your table do not line up at all. Are your comments based on some other data?

myisam/falcon = 11.208661
innodb/falcon = 1.188976

Where did you get your 143x and 176x numbers?

]]> Comment on SHOW PROFILES in MySQL 5.1 by Jeremy Cole http://blogs.mysql.com/gmax/2007/11/14/show-profiles-in-mysql-51/#comment-7 Jeremy Cole Thu, 15 Nov 2007 19:42:41 +0000 http://blogs.mysql.com/gmax/2007/11/14/show-profiles-in-mysql-51/#comment-7 Hi Giuseppe, No offense was taken. Actually, I just looked at the code you provided as 5.1.23. There are basically no changes from 5.0... The only diffs are because of changes in 5.1, and a new macro COMMUNITY_SERVER. What do you mean 80% of the code has changed? The thd->proc_info to thd_proc_info() macro change is obvious, and yes this accounts for actually closer to 99% of the patch size by line, but it is for the most part a trivial search and replace. The macro should have been implemented in 5.1 a long long time ago actually. I would not say that the implementation has "evolved" at all... Regards, Jeremy Hi Giuseppe,

No offense was taken. Actually, I just looked at the code you provided as 5.1.23. There are basically no changes from 5.0… The only diffs are because of changes in 5.1, and a new macro COMMUNITY_SERVER. What do you mean 80% of the code has changed?

The thd->proc_info to thd_proc_info() macro change is obvious, and yes this accounts for actually closer to 99% of the patch size by line, but it is for the most part a trivial search and replace. The macro should have been implemented in 5.1 a long long time ago actually.

I would not say that the implementation has “evolved” at all…

Regards,

Jeremy

]]>