tag:blogger.com,1999:blog-9144505959002328789.post5616209845749982828..comments2024-03-29T08:14:29.447+01:00Comments on Karlsson on databases and stuff: More on Stored Procedure performanceKarlssonhttp://www.blogger.com/profile/04874338187076980133noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-9144505959002328789.post-14385702661988398202009-02-17T22:44:00.000+01:002009-02-17T22:44:00.000+01:00Actually, I was thinging of trying a few options f...Actually, I was thinging of trying a few options for the loop in this procedure. I have some ideas for that. Instead of the simple increment maybe there is another option to do this that might be faster? I think we have a simple framework for some basic testing here.<BR/><BR/>/KarlssonKarlssonhttps://www.blogger.com/profile/04874338187076980133noreply@blogger.comtag:blogger.com,1999:blog-9144505959002328789.post-60196156377027904222009-02-17T21:26:00.000+01:002009-02-17T21:26:00.000+01:00"Do as little computational stuff as possible in a..."Do as little computational stuff as possible in any <B>MySQL</B> procedure"<BR/><BR/>There, fixed that for ya ;)<BR/><BR/>Ok - jokes aside. I don't care so much about the procedures, but isn't this the axe for mysql stored functions? Argueably the point of those is computation. Is there anything that can be done to fix this? Beat Vontobel had a really smart and straighforward idea to use a kind of 'macro-optimization' to improve stored function performance, is there anyone interested to build this?rpboumanhttps://www.blogger.com/profile/13365137747952711328noreply@blogger.com