The documentation Creating graphs in the catalog claims such performance advantange when using Native Projection over Cypher Projection, but does not give much explanation.
Native projection
Provides the best performance...Cypher projection
The more flexible, expressive approach with lesser focus on performance.
As I understand, all projections will end up:
Graph projections are stored entirely in-memory using compressed data structures optimized for topology and property lookup operations.
So why is the performance gain?
In addition, the assumed gained performance is for loading (materialize) the projected graph or later for processing, e.g. with PageRank algorithm?