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

Clustered sizing recommendations per vendor #5652

Merged
merged 3 commits into from
Oct 21, 2024

Conversation

sanderson
Copy link
Collaborator

  • Rebased/mergeable

Copy link
Contributor

@jstirnaman jstirnaman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! 1 minor unrelated fix.

Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>
@@ -88,14 +88,89 @@ InfluxDB Clustered Kubernetes deployments require `kubectl` 1.27 or higher.
### Cluster sizing recommendation

For a [medium-sized workload](https://www.influxdata.com/resources/influxdb-3-0-vs-oss/),

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this the correct link? I went to the linked doc, but it didn't seem to say anything about a medium sized workload.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this was the link that was in the original installation google doc. I assume it's referring to the workload used in the benchmarking the white-paper covers.

Edit: I just read through the white-paper and it doesn't ever explicitly outline the workload. It describes how the workload was increased until degradation was observed in each product. I think I'll just take this link out.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@barbaranelson I don't have any insight into what comprises a medium workload, but in the 1.x hardware sizing doc, we state this for those considering single node OSS vs Enterprise:

If your InfluxDB performance requires any of the following, a single node (InfluxDB OSS) may not support your needs:

  • more than 750,000 field writes per second
  • more than 100 moderate queries per second

Is this in the ballpark of what we would consider a medium workload?

Copy link

@barbaranelson barbaranelson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Thanks.

@sanderson sanderson merged commit 89d65c0 into clustered/install-reorg Oct 21, 2024
1 check passed
@sanderson sanderson deleted the clustered/sizing-reqs branch October 21, 2024 14:56
sanderson added a commit that referenced this pull request Oct 21, 2024
* WIP clustered install restructure

* WIP clustered install restructure

* WIP clustered install reorg

* finalize clustered install reorg for preview

* updates to address PR feedback

* added garbage collector scaling config

* Apply suggestions from code review

Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>

* removed obsolete api artifacts

* remove callouts for specific dependency versions

* Clustered sizing recommendations per vendor (#5652)

* added vendor-specific sizing recommendations to clustered

* Apply suggestions from code review

Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>

* remove medium-sized workload link

---------

Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>

---------

Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>
jstirnaman added a commit that referenced this pull request Oct 25, 2024
* WIP clustered install restructure

* WIP clustered install restructure

* WIP clustered install reorg

* finalize clustered install reorg for preview

* updates to address PR feedback

* added garbage collector scaling config

* Apply suggestions from code review

Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>

* removed obsolete api artifacts

* remove callouts for specific dependency versions

* Clustered sizing recommendations per vendor (#5652)

* added vendor-specific sizing recommendations to clustered

* Apply suggestions from code review

Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>

* remove medium-sized workload link

---------

Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>

---------

Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>
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

Successfully merging this pull request may close these issues.

3 participants