Remove hard upper memory limits from FAQ and ClickHouse docs

[jcaw07]

Summary

Docs should not state a hard upper memory limit, per the GTM/Prod/Eng sync on 2026-09-15. This PR updates two pages:

• docs/about/faq.md (/docs/about/faq): "scale vertically to large 768GB machines with 64 cores" now reads "scale vertically to the largest multi-terabyte machines."
• docs/integrations/clickhouse.md (/docs/integrations/clickhouse): "Dragonfly is able to support up to 1TB on a single instance" now reads "Dragonfly supports multi-terabyte datasets on a single instance." The sentence calling 1TB not "big data" is deleted.

Related

The matching website copy changes are in dragonflydb/website-cms#278.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
documentation	Ready	Preview	Sep 29, 2026 11:06pm UTC

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can add REVIEW.md to your repo root and Qodo follows it on every PR

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-free-for-open-source-projects]

PR Summary by Qodo

Remove fixed memory ceilings from FAQ and ClickHouse docs

📝 Documentation 🕐 Less than 5 minutes

AI Description

• Replace fixed single-instance size claims with multi-terabyte scaling language in two
 documentation pages.
• Remove the ClickHouse page’s outdated qualification of 1TB as “big data.”

High-Level Assessment

Directly revising the two affected passages is appropriate; the changes do not warrant an architectural alternative.

Files changed (2) +2 / -3

Documentation (2) +2 / -3

faq.mdRemove the FAQ’s 768GB scaling figure +1/-1

Remove the FAQ’s 768GB scaling figure

• Replaces the 768GB and 64-core machine example with language describing vertical scaling to multi-terabyte machines.

docs/about/faq.md

clickhouse.mdRemove the ClickHouse guide’s 1TB ceiling +1/-2

Remove the ClickHouse guide’s 1TB ceiling

• Describes multi-terabyte datasets on a single Dragonfly instance instead of a 1TB limit. Removes the sentence qualifying whether 1TB counts as big data.

docs/integrations/clickhouse.md