What is the execution path for replicated tables? I realize it's not optimal, but if you had a large dimension replicated across the nodes and you wanted to execute a count(*) against that table (no filter and no join), would the engine attempt to resolve it through one node or would all nodes contribute?
In the case of replicated tables, it will pick one node and just execute the statement on one.
Note that since GridSQL uses PostgreSQL, count may be a little slow. PostgreSQL is known for executing counts a little bit slowly due to its Multi-version Concurrency Control; it verifies the visibility of each tuple for the current transaction context (snapshot).