[MCOL-1411] Document how to decide value for VersionBufferFileSize Created: 2018-05-14 Updated: 2023-07-02 Resolved: 2023-07-02 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | N/A |
| Affects Version/s: | 1.1.4 |
| Fix Version/s: | Icebox |
| Type: | Task | Priority: | Minor |
| Reporter: | Geoff Montee (Inactive) | Assignee: | Richard Stracke |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | documentation | ||
| Issue Links: |
|
||||||||
| Description |
|
The documentation has some details on VersionBufferFileSize:
https://mariadb.com/kb/en/library/columnstore-batch-insert-mode/#version-buffer-file-management There are also some more details here: We should probably also add details on how to come up with an optimal value. It sounds like each block updated by a transaction requires 40 bytes in the version buffer, so it sounds like the optimal value might depend on:
If the optimal value depends on many different factors, is there a good way to generalize a method to determine the optimal value, or is it something that should be set by trial and error? Can the error message in the log give some clue on how to decide the optimal value?:
|
| Comments |
| Comment by Andrew Hutchings (Inactive) [ 2018-05-14 ] |
|
Should also be updated to say that an UPDATE or DELETE is way more likely to require a large version buffer. LDI and INSERT...SELECT only use version buffer if they are part of a transaction. |
| Comment by Todd Stoffel (Inactive) [ 2023-07-02 ] |
|
The "create date" on this ticket is pre-convergence with MariaDB server. If the issue still exists in a modern version of the engine/plugin please submit a new ticket. |