This concerns me, and I am glad that I have worked around this for the most part with multiple GraphQL queries on client side that I chain together.
I have 27K+ contacts. Each contact will normally have 1 address linking node, but could have an unlimited amount. Each address linking node links to an address node, each address node links to a state node. These state nodes are deduplicated to keep reverse lookups easier to all addresses in a state, but to continue on with this example. If I want to find contacts given a state in their address, this would query 27K + >27K + >27K + ~50. And this would return the ~540 in the state I am looking for. This costs querying 81,050+ nodes to get to this point. Using the inverse relationships in my work around I query 1 state + 540 addresses + 540 address linking nodes + 540 contacts. 1,621 nodes touched vs. 81,050. Just my opinion, but if this is the only way to do it right now, then maybe this should be held off for now. Better not done, then done with poor performance.