CN scaling and performance verification

Additional CNs can spread sessions and add capacity for distributed queries. Session routing, operator placement and remote caching are separate processes. FileService fetching file ranges from another CN does not forward SQL to that CN. Eviction follows the actual implementation and is not universally LRU.

Acceptance

Hold SQL, data, plans, hardware, concurrency and storage constant. Record p50/p95 latency, throughput, CPU, scans/bytes, remote execution and cache state. Test session distribution separately from one query’s actual remote fragments. New nodes need synchronization/cache warming; active transactions and session migration need separate checks.

See cluster scaling and FileService.