[MCOL-4038] Tool to predict the final storage requirements Created: 2020-06-04 Updated: 2021-04-19 Resolved: 2020-12-02 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | N/A |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | New Feature | Priority: | Minor |
| Reporter: | Todd Stoffel (Inactive) | Assignee: | Todd Stoffel (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Description |
|
A request came from a customer to provide a tool or algorithm that will help them predict the final storage requirements. Their current setup is 2 UMs and 3 PMs they expect to ingest about 1Gb/hour. |
| Comments |
| Comment by Nick (Inactive) [ 2020-11-23 ] | ||||||||||||
|
Is there some simple math we can do based off of their dataset / row size and/or current innodb (assumed) dataset? Thinking this could be a simple documentation item if a tool didn't make sense in the short-term. | ||||||||||||
| Comment by Todd Stoffel (Inactive) [ 2020-12-02 ] | ||||||||||||
|
| ||||||||||||
| Comment by Todd Stoffel (Inactive) [ 2020-12-02 ] | ||||||||||||
|
This can be done currently by querying the InnoDB table size (without indexes) and accounting for minimum compression. |