tag:blogger.com,1999:blog-15319370.post5143075881089073580..comments2024-03-29T12:51:32.931+01:00Comments on Roland Bouman's blog: So, are Database Stored Procedures Good or Bad?rpboumanhttp://www.blogger.com/profile/13365137747952711328noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-15319370.post-9740954572921492222007-09-28T02:17:00.000+02:002007-09-28T02:17:00.000+02:00Thanks for your nice post! Keep it upThanks for your nice post! Keep it upAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-15319370.post-3097135487744956782007-03-13T17:49:00.000+01:002007-03-13T17:49:00.000+01:00Hi Jay,thanks for your reply.Actually I wanted to ...Hi Jay,<BR/><BR/>thanks for your reply.<BR/><BR/>Actually I wanted to write that article ever since I read <A HREF="http://www.jpipes.com/index.php?/archives/54-Do-the-New-Features-of-MySQL-5-Cause-Performance-Degradation.html" REL="nofollow">your article</A> on MySQL Stored Procedure Performance ;) So thank you for the inspiration. <BR/><BR/>Regarding portability: I have a few thoughts about it, but I can give it away now: it has to do with what you want to port, the application or the database.<BR/><BR/>BTW, On <A HREF="http://www.oreillynet.com/databases/blog/2007/03/_so_are_database_stored_proced.html" REL="nofollow">the O'Reilly blog</A>, I already got a comment from an individual that is very outspoken in the increased portabilityrpboumanhttps://www.blogger.com/profile/13365137747952711328noreply@blogger.comtag:blogger.com,1999:blog-15319370.post-53620647641649564102007-03-13T17:33:00.000+01:002007-03-13T17:33:00.000+01:00Really interesting results, Roland! Thanks for po...Really interesting results, Roland! Thanks for posting them. Not sure why anyone would think that stored procedures make portability *better* ?! All RDBMS system implement a sub or super-set of ANSI, so portability is virtually killed with stored procedures ;)<BR/><BR/>As for performance, it's an interesting subject. I was the one that answered "For MySQL, totally depends..." because for simple procedures that *are not repeatedly executed on ***every*** connection, there is little performance benefit. Why? Because, unlike every major RDBMS implementation of an SP cache, MySQL puts the cache in the connection thread, not a global cache. What effects does this have? Well, stored procedures have to be recompiled for each connection thread... therefore you aren't really gaining any benefits of SP compilation if you just execute a SP once per connection. But, by the same token, lock contention for stored procedure compilation and caching is much less in MySQL than with other systems since the thread itself manages a cache of the SPs, not a global manger, which requires no lock management for various requesting threads. It will be interesting to see how this benefit/disadvantage is handled in the future coding of the SP source...<BR/><BR/>Anyway, looking forward to your article!<BR/><BR/>CheersUnknownhttps://www.blogger.com/profile/16581538991015419636noreply@blogger.com