| Bug #114468 | Inconsistent table performance: fresh data import vs after optimization | ||
|---|---|---|---|
| Submitted: | 24 Mar 21:51 | Modified: | 25 Mar 16:44 |
| Reporter: | Przemyslaw Malkowski | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S5 (Performance) |
| Version: | 8.3.0, 8.0.36 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
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
[25 Mar 15:38]
Umesh Shastry
[9 Apr 6:25]
huahua xu
The patch would specify the expected page number for a new allocating page during rebuilding B-tree index for bulk load.
Attachment: hint_page_no_for_page_load.patch (application/octet-stream, text), 2.83 KiB.
