Home » Performance » MySQL » Overhead of stored procs
Overhead of stored procs [message #375] Tue, 21 November 2006 03:52 Go to previous message
carpii  is currently offline carpii
Messages: 48
Registered: November 2006
Member
Hi, what are your thoughts on the benefits to be had from stored procs?

Im from an MS SQL background, and the benefits there are quite clear. But several places I read about MySQL Stored Procs and they warn 'there is an overhead of stored procs because some of the processing moves from the client to the server'.

I dont really understand this.
What overhead does using a precompiled stored procs involve?
Is it referring to the overhead of dynamically building the query, and if so why would this be an issue other than the first time its run (ie compiled)?

For the purposes of my question, pleae ignore the benefits of stored procs caused by reduced network traffic and all security issues. Im aware stored procs can often provoke a religious debate Smile

Im talking purely about the caching of compiled batches, which is the performance benefit Im hoping to gain on my heavily used website

Thanks
Carpii

[Updated on: Tue, 21 November 2006 03:53]

Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic:Row-Level Replication in MySQL 5.0 (by the application level)
Next Topic:How many times are my indexes used?
Goto Forum:

  


Current Time: Thu Jul 9 22:03:12 EDT 2009

Total time taken to generate the page: 0.10324 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 2.7.7.
Copyright ©2001-2007 FUD Forum Bulletin Board Software

MySQL is a trademark of Sun Microsystems.
InnoDB is a trademark of Oracle Corp.

Percona Performance Forums are a service of Percona, Inc.
Not affiliated with Sun Microsystems or Oracle Corp.