docs: document Community single-core Neo4j limitation
Merged
ID
4mo ago+2+2+0123456789-0-0-0123456789
What
Documents the Community Edition single-core Neo4j limitation on the Community vs enterprise page. Adds a Database concurrency point to both the Community characteristics and Enterprise enhancements lists:
- Community: Neo4j runs on a single CPU core, so large merges and imports are bound by single-core performance regardless of host core count.
- Enterprise: multi-core Neo4j for parallel query and merge execution.
Why
This is the concrete mechanism behind the edition performance difference, and it was not stated anywhere in the docs (a repo-wide search for "single core" returned nothing). The page previously explained the gap only in general terms (device counts, vertical vs horizontal scaling), leaving readers without the actual reason large merges slow down on Community.
Reviewer attention
- Placed as a factual bullet in the existing Performance and scalability lists — no structural change.
- Pairs with the hardware requirements local-evaluation section (separate PR), which links here for the scaling story.