| Bug #107327 | High Memory Usage When Running Stored Procedure | ||
|---|---|---|---|
| Submitted: | 18 May 2022 11:51 | Modified: | 5 Oct 2022 17:41 |
| Reporter: | Steven Azzopardi | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Stored Routines | Severity: | S2 (Serious) |
| Version: | 8.0.27, 8.0.28, 8.0.29 | OS: | Linux |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | regression | ||
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
[18 May 2022 11:52]
Steven Azzopardi
[18 May 2022 11:52]
Steven Azzopardi
Stored Procedure
Attachment: processor_pending_SP.sql (application/octet-stream, text), 609 bytes.
[20 May 2022 12:27]
Shane Bester
8.0.29 memory heap profile
Attachment: mybin.hprof.0238.heap.pdf (application/pdf, text), 23.33 KiB.
[20 May 2022 12:30]
Shane Bester
.txt heap profile of 8.0.29
Attachment: mybin.hprof.0238.heap.zip (application/zip, text), 1.10 MiB.
