Papers › Experimental Evaluation of Distributed k-Core Decomposition
Experimental Evaluation of Distributed k-Core Decomposition
Bin Guo, Runze Zhao
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
Given an undirected graph, the k-core is a subgraph in which each node has at least k connections. This is widely used in graph analytics to identify core subgraphs within a larger graph. The sequential k-core decomposition algorithm faces limitations due to memory constraints, and many data graphs are inherently distributed. A distributed approach is proposed to overcome limitations by allowing each vertex to compute its core number independently using only local information. This work explores the experimental evaluation of a distributed k-core decomposition algorithm. By assuming that each vertex is a client as a single computing unit, we simulate the process using Golang, leveraging its Goroutines and message passing. Since real-world data graphs can be large with millions of vertices, it is expensive to build a distributed environment with millions of clients if experiments were run in a real distributed environment. Therefore, our experimental simulation can effectively evaluate the running time and message passing for the distributed k-core decomposition.
Code
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.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
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