When normalization hurts: An empirical study on layer stacking in graph neural networks


Abstract

Normalization layers are widely adopted to stabilize and accelerate the training of deep learning models, yet their influence on Graph Neural Networks (GNNs) is not uniformly beneficial. This work presents a seed-controlled, depth-swept empirical study that examines when normalization helps and when it hurts. Across six public node-classification benchmarks and a full depth range from 1 to 10 layers, we evaluate six normalization schemes—NoNorm, BatchNorm, GraphNorm, LayerNorm, NodeNorm, and PairNorm. Each configuration is trained under five random seeds, totaling 1,400 runs. Our analysis yields three key findings: (i) Normalization does not consistently improve shallow-layer accuracy, though it often reduces seed-to-seed variance, indicating enhanced stability rather than systematic gain. (ii) As depth increases, this stabilizing effect weakens, and several normalization methods exacerbate the performance decline instead of mitigating it. (iii) The onset and severity of deterioration vary across datasets, reflecting differences in graph density and feature distribution. Overall, our results reveal a clear depth-dependent trade-off: normalization can stabilize training in early regimes but may distort representation statistics and degrade accuracy when layers are stacked too deeply.
Ask to review this manuscript

Notes for potential reviewers

  • Volunteering is not a guarantee that you will be asked to review. There are many reasons: reviewers must be qualified, there should be no conflicts of interest, a minimum of two reviewers have already accepted an invitation, etc.
  • This is NOT OPEN peer review. The review is single-blind, and all recommendations are sent privately to the Academic Editor handling the manuscript. All reviews are published and reviewers can choose to sign their reviews.
  • What happens after volunteering? It may be a few days before you receive an invitation to review with further instructions. You will need to accept the invitation to then become an official referee for the manuscript. If you do not receive an invitation it is for one of many possible reasons as noted above.

  • PeerJ Computer Science does not judge submissions based on subjective measures such as novelty, impact or degree of advance. Effectively, reviewers are asked to comment on whether or not the submission is scientifically and technically sound and therefore deserves to join the scientific literature. Our Peer Review criteria can be found on the "Editorial Criteria" page - reviewers are specifically asked to comment on 3 broad areas: "Basic Reporting", "Experimental Design" and "Validity of the Findings".
  • Reviewers are expected to comment in a timely, professional, and constructive manner.
  • Until the article is published, reviewers must regard all information relating to the submission as strictly confidential.
  • When submitting a review, reviewers are given the option to "sign" their review (i.e. to associate their name with their comments). Otherwise, all review comments remain anonymous.
  • All reviews of published articles are published. This includes manuscript files, peer review comments, author rebuttals and revised materials.
  • Each time a decision is made by the Academic Editor, each reviewer will receive a copy of the Decision Letter (which will include the comments of all reviewers).

If you have any questions about submitting your review, please email us at [email protected].