Papers › Graph Convolutional Neural Networks for Web-Scale Recommender Systems

Graph Convolutional Neural Networks for Web-Scale Recommender Systems

6 Jun 2018arXiv:1806.01973archive 2025-07-28

Rex Ying, Ruining He, Kai-Feng Chen, Pong Eksombatchai, William L. Hamilton, Jure Leskovec

Recent advancements in deep neural networks for graph-structured data have led to state-of-the-art performance on recommender system benchmarks. However, making these methods practical and scalable to web-scale recommendation tasks with billions of items and hundreds of millions of users remains a challenge. Here we describe a large-scale deep recommendation engine that we developed and deployed at Pinterest. We develop a data-efficient Graph Convolutional Network (GCN) algorithm PinSage, which combines efficient random walks and graph convolutions to generate embeddings of nodes (i.e., items) that incorporate both graph structure as well as node feature information. Compared to prior GCN approaches, we develop a novel method based on highly efficient random walks to structure the convolutions and design a novel training strategy that relies on harder-and-harder training examples to improve robustness and convergence of the model. We also develop an efficient MapReduce model inference algorithm to generate embeddings using a trained model. We deploy PinSage at Pinterest and train it on 7.5 billion examples on a graph with 3 billion nodes representing pins and boards, and 18 billion edges. According to offline metrics, user studies and A/B tests, PinSage generates higher-quality recommendations than comparable deep learning and graph-based alternatives. To our knowledge, this is the largest application of deep graph embeddings to date and paves the way for a new generation of web-scale recommender systems based on graph convolutional architectures.

PaperPDFCodeCode Syntology ranMethod as code

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 11 code samples harvested from 3 repositories linked to this paper: 3 ran (of which 1 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 0 where Syntology's instrument failed) · 8 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 11 samples from 3 repositories, 3 ran (3 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-22 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

massquantity/LibRecommender mentioned on GitHubtfMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Self-supervised Learning for Large-scale Item Recommendations (arXiv:2007.12865; that paper's own run record: 2 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report
wei9711/d2gcn mentioned on GitHubpytorchSyntology: not harvested report
yoonjong12/pinsage mentioned on GitHubpytorchMITSyntology: 4 samples, 2 ran (0 instrument-failed) · 2 unverified report
breadbread1984/PinSage-tf2.0 tfSyntology: 2 samples, 1 ran (0 instrument-failed) · 1 unverified report
dmlc/dgl pytorchSyntology: 5 samples, 0 ran · 5 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

11 samples harvested: 3 ran (of which 1 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 0 where Syntology's instrument failed) · 8 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

3ran
8unverified

Licence: 2 of the 11 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 3 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

yoonjong12/pinsage community (archive-listed) 4 samples, 2 ran (0 instrument-failed) · 2 unverified
get_blocks in 39 papers evaluation.py ran MIT (permissive) · 896a6c529fb43b9d · report fixture: signature seeds:list/1/int, item_ntype:str/0/str, textset:MinimalTextSet/0/?, sampler:MinimalSampler/0/? · returned list · level recorded 2026-09-26
node_to_item evaluation.py ran MIT (permissive) · 302c59855b3fbcec · report fixture: signature nodes:list/1/int, id_dict:dict/0/?, cateogry_dict:dict/0/? · returned list · level recorded 2026-09-26
build_val_test_matrix data_utils.py unverified MIT (permissive) · 1eefc35490de45cd · report
check_param_num evaluation.py unverified MIT (permissive) · dfc097b3bdb4acb8 · report
breadbread1984/PinSage-tf2.0 community (archive-listed) 2 samples, 1 ran (0 instrument-failed) · 1 unverified
Convolve PinSage.py ran no licence file found · pointer only · 96d53e8419ea0290 · report fixture: returned Convolve · level recorded 2026-09-22
PinSage PinSage.py unverified no licence file found · pointer only · 5557298b5b513f28 · report
dmlc/dgl community (archive-listed) 5 samples, 0 ran · 5 unverified
DGLError python/dgl/sampling/pinsage.py unverified Apache-2.0 (permissive) · 306abff4458ab700 · report
PinSAGESampler python/dgl/sampling/pinsage.py unverified Apache-2.0 (permissive) · 892b9254565cb7c5 · report
RandomWalkNeighborSampler python/dgl/sampling/pinsage.py unverified Apache-2.0 (permissive) · 8cbd0b0d003b05e9 · report
_select_pinsage_neighbors python/dgl/sampling/pinsage.py unverified Apache-2.0 (permissive) · 7cacf32da5bfdf02 · report
random_walk in 12 papers python/dgl/sampling/pinsage.py unverified Apache-2.0 (permissive) · 03c3e3f5dfa7773a · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it. Siblings are assemblies lifted from this paper in the same batch for the same method: alternative readings kept side by side; none replaces or supersedes another.

2 assemblies on this paper: 2 harvested, 0 generated, listed in 1 groups (siblings lifted in one batch form one group).

2 sibling assemblies for PinSage (harvested), lifted in the same batch on 2026-09-09: alternative readings kept side by side; none replaces or supersedes another.

harvested Assembly for PinSage (graph method: PinSage). 2 bricks; individually on a fixture: 1 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified; the one sample that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.

one of 2 siblings

  1. PinSage entry · level 0 · unverified · 5557298b5b513f28
  2. Convolve model · level 1 · ran · 96d53e8419ea0290

harvested Assembly for PinSage (graph method: PinSage). 5 bricks; individually on a fixture: 0 ran · 5 unverified. The assembly has not been run end-to-end.

one of 2 siblings

  1. PinSAGESampler entry · level 0 · unverified · 892b9254565cb7c5
  2. RandomWalkNeighborSampler sampler · level 0 · unverified · 8cbd0b0d003b05e9
  3. _select_pinsage_neighbors helper · level 0 · unverified · 7cacf32da5bfdf02
  4. random_walk helper · level 0 · unverified · 03c3e3f5dfa7773a
  5. DGLError helper · level 0 · unverified · 306abff4458ab700

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="1806.01973") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Recommendation Systems

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections