Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Change] Add capacity planning information #584

Open
wilfriedroset opened this issue Nov 12, 2020 · 1 comment
Open

[Change] Add capacity planning information #584

wilfriedroset opened this issue Nov 12, 2020 · 1 comment

Comments

@wilfriedroset
Copy link
Contributor

Change in content, appearance, or functionality?
Add the appropriate label(s) -->>

Describe the change
While researching information about TSDB solution ones might need to have capacity planning information.
Obviously, this depends significantly on usecases but ballpark figures can help assess the solution, in this case timescaledb.

Based on the tutorial sample datasets one can have a disk space estimation:

devices_small=# \l+ devices_small
                                                    List of databases
     Name      |  Owner   | Encoding |   Collate   |    Ctype    | Access privileges |  Size   | Tablespace | Description
---------------+----------+----------+-------------+-------------+-------------------+---------+------------+-------------
 devices_big | tutorial | UTF8     | en_US.UTF-8 | en_US.UTF-8 |                   | 7661 MB | pg_default |
(1 row)

For 3,000 devices recorded over 10,000 time intervals, we have 30000000 datapoints for a total of 7661 MB.

TimescalDB's expert advices would be appreciated for that especially for RAM and CPU.
We can find such documentation in several solutions:

Location(s)

I believe a dedicated page is best suited

How soon is this needed?

@jonatas
Copy link

jonatas commented Apr 28, 2021

Thank you for the suggestion @wilfriedroset! It's already on our radar and we're going to put it in our roadmap. I'll share the link when we publish the first version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants