MySQL Bugs: #91585: “dead” code inside the stored proc or function can significantly slow it down

Bug #91585	“dead” code inside the stored proc or function can significantly slow it down
Submitted:	10 Jul 2018 1:16	Modified:	10 Jul 2018 9:39
Reporter:	Alexander Rubin	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Stored Routines	Severity:	S5 (Performance)
Version:	5.7, 8.0, 8.0.11, 5.7.23	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	performance, stored function, stored procedure, trigger

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

Func1,a trace with ps_trace_thread() procedure

Attachment: func1.png (image/png, text), 333.83 KiB.

Func2, a trace with ps_trace_thread() procedure

Attachment: func2.png (image/png, text), 333.00 KiB.

Func3, a trace with ps_trace_thread() procedure

Attachment: func3.png (image/png, text), 460.01 KiB.