Why MySQL Stored Procedures, Functions and Triggers Are Bad For Performance

MySQL stored procedures, functions and triggers are tempting constructs for application developers. However, as I discovered, there can be an impact on database performance when using MySQL stored routines. Not being entirely sure of what I was seeing during a customer visit, I set out to create some simple tests to measure the impact of triggers on database performance. The outcome might surprise you.

Why stored routines are not optimal performance wise: short version

Recently, I worked with a customer to profile the performance of triggers and stored routines. What I’ve learned about stored routines: “dead” code (the code in a branch which will never run) can still significantly slow down the response time of a function/procedure/trigger. We will need to be careful to clean up what we do not need.

Profiling MySQL stored functions

Let’s compare these four simple stored functions (in MySQL 5.7):

Function 1:

This function simply declares a variable and returns it. It is a dummy function

Function 2:

This function calls another function, levenshtein_limit_n (calculates levenshtein distance). But wait: this code will never run – the condition IF 1=2 will never be true. So that is the same as function 1.

Function 3:

Here there are four conditions and none of these conditions will be true: there are 4 calls of “dead” code. The result of the function call for function 3 will be the same as function 2 and function 1.

Function 4:

This is the same as function 3 but the function we are running does not exist. Well, it does not matter as the
select does_not_exit  will never run.

So all the functions will always return 0. We expect that the performance of these functions will be the same or very similar. Surprisingly it is not the case! To measure the performance I used the “benchmark” function to run the same function 1M times. Here are the results:

As we can see func3 (with four dead code calls which will never be executed, otherwise identical to func1) runs almost 3x slower compared to func1(); func3_nope() is identical in terms of response time to func3().

Visualizing all system calls from functions

To figure out what is happening inside the function calls I used performance_schema / sys schema to create a trace with ps_trace_thread() procedure

1. Get the thread_id for the MySQL connection:

   mysql> select THREAD_ID from performance_schema.threads where processlist_id = connection_id(); +———–+ | THREAD_ID | +———–+ |        49 | +———–+ 1 row in set (0.00 sec)

2. Run ps_trace_thread in another connection passing the thread_id=49:

   mysql> CALL sys.ps_trace_thread(49, concat(‘/var/lib/mysql-files/stack-func1-run1.dot’), 10, 0, TRUE, TRUE, TRUE); +——————–+ | summary            | +——————–+ | Disabled 0 threads | +——————–+ 1 row in set (0.00 sec)   +———————————————+ | Info                                        | +———————————————+ | Data collection starting for THREAD_ID = 49 | +———————————————+ 1 row in set (0.00 sec)

3. At that point I switched to the original connection (thread_id=49) and run:

   mysql> select func1(); +————–+ | func1() | +————–+ |       0 | +————–+ 1 row in set (0.00 sec)

4. The sys.ps_trace_thread collected the data (for 10 seconds, during which I ran the
   select func1() ), then it finished its collection and created the dot file:

   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

   +———————————————————————–+ | Info                                                                  | +———————————————————————–+ | Stack trace written to /var/lib/mysql–files/stack–func3nope–new12.dot | +———————————————————————–+ 1 row in set (9.21 sec)   +——————————————————————————-+ | Convert to PDF                                                                | +——————————————————————————-+ | dot -Tpdf -o /tmp/stack_49.pdf /var/lib/mysql–files/stack–func3nope–new12.dot | +——————————————————————————-+ 1 row in set (9.21 sec)   +——————————————————————————-+ | Convert to PNG                                                                | +——————————————————————————-+ | dot -Tpng -o /tmp/stack_49.png /var/lib/mysql–files/stack–func3nope–new12.dot | +——————————————————————————-+ 1 row in set (9.21 sec)   Query OK, 0 rows affected (9.45 sec)

I repeated these steps for all the functions above and then created charts of the commands.

Here are the results:

Func1()

Func2()

Func3()

 

As we can see there is a sp/jump_if_not call for every “if” check followed by an opening tables statement (which is quite interesting). So parsing the “IF” condition made a difference.

For MySQL 8.0 we can also see MySQL source code documentation for stored routines which documents how it is implemented. It reads:

Flow Analysis Optimizations
After code is generated, the low level sp_instr instructions are optimized. The optimization focuses on two areas:

Dead code removal,
Jump shortcut resolution.
These two optimizations are performed together, as they both are a problem involving flow analysis in the graph that represents the generated code.

The code that implements these optimizations is sp_head::optimize().

However, this does not explain why it executes “opening tables”. I have filed a bug.

When slow functions actually make a difference

Well, if we do not plan to run one million of those stored functions we will never even notice the difference. However, where it will make a difference is … inside a trigger. Let’s say that we have a trigger on a table: every time we update that table it executes a trigger to update another field. Here is an example: let’s say we have a table called “form” and we simply need to update its creation date:

That is good and fast. Now we create a trigger which will call our dummy func1():

Now repeat the update. Remember: it does not change the result of the update as we do not really do anything inside the trigger.

Just adding a dummy trigger will add 2x overhead: the next trigger, which does not even run a function, introduces a slowdown:

Now, lets use func3 (which has “dead” code and is equivalent to func1):

However, running the code from the func3 inside the trigger (instead of calling a function) will speed up the update:

Memory allocation

Potentially, even if the code will never run, MySQL will still need to parse the stored routine—or trigger—code for every execution, which can potentially lead to a memory leak, as described in this bug.

Conclusion

Stored routines and trigger events are parsed when they are executed. Even “dead” code that will never run can significantly affect the performance of bulk operations (e.g. when running this inside the trigger). That also means that disabling a trigger by setting a “flag” (e.g.
if @trigger_disable = 0 then ... ) can still affect performance of bulk operations.

Related