On the Bottleneck of Graph Neural Networks and its Practical Implications

Uri Alon, Eran Yahav
6/9/2020
cs.LGstat.ML

Official code: tech-srl/bottleneck (100 stars, MIT, last commit 2022-04-25).

Abstract

Since the proposal of the graph neural network (GNN) by Gori et al. (2005) and Scarselli et al. (2008), one of the major problems in training GNNs was their struggle to propagate information between distant nodes in the graph. We propose a new explanation for this problem: GNNs are susceptible to a bottleneck when aggregating messages across a long path. This bottleneck causes the over-squashing of exponentially growing information into fixed-size vectors. As a result, GNNs fail to propagate messages originating from distant nodes and perform poorly when the prediction task depends on long-range interaction. In this paper, we highlight the inherent problem of over-squashing in GNNs: we demonstrate that the bottleneck hinders popular GNNs from fitting long-range signals in the training data; we further show that GNNs that absorb incoming edges equally, such as GCN and GIN, are more susceptible to over-squashing than GAT and GGNN; finally, we show that prior work, which extensively tuned GNN models of long-range problems, suffers from over-squashing, and that breaking the bottleneck improves their state-of-the-art results without any tuning or additional weights. Our code is available at https://github.com/tech-srl/bottleneck/ .

View on arXivView PDF

Code Implementations(1)

MIT

Code for the paper: "On the Bottleneck of Graph Neural Networks and Its Practical Implications"

10023Python, Jupyter NotebookSep 4, 20204 years agoMIT
bottleneckgnnsgraphnetworksneural+5 more

Cite this paper

@article{alon2020bottleneck,
  title  = {On the Bottleneck of Graph Neural Networks and its Practical Implications},
  author = {Uri Alon and Eran Yahav},
  year   = {2020},
  eprint = {2006.05205},
  archivePrefix = {arXiv},
  url    = {https://arxiv.org/abs/2006.05205}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2006.05205.svg)](https://codeofpaper.com/paper/2006.05205)

Discussion