Graph (abstract data type)

Short description: Abstract data type in computer science

A directed graph with three vertices (blue circles) and three edges (black arrows).

In computer science, a graph is an abstract data type that is meant to implement the undirected graph and directed graph concepts from the field of graph theory within mathematics.

A graph data structure consists of a finite (and possibly mutable) set of vertices (also called nodes or points), together with a set of unordered pairs of these vertices for an undirected graph or a set of ordered pairs for a directed graph. These pairs are known as edges (also called links or lines), and for a directed graph are also known as edges but also sometimes arrows or arcs. The vertices may be part of the graph structure, or may be external entities represented by integer indices or references.

A graph data structure may also associate to each edge some edge value, such as a symbolic label or a numeric attribute (cost, capacity, length, etc.).

Operations

The basic operations provided by a graph data structure G usually include:

• adjacent(G, x, y): tests whether there is an edge from the vertex x to the vertex y;
• neighbors(G, x): lists all vertices y such that there is an edge from the vertex x to the vertex y;
• add_vertex(G, x): adds the vertex x, if it is not there;
• remove_vertex(G, x): removes the vertex x, if it is there;
• add_edge(G, x, y, z): adds the edge z from the vertex x to the vertex y, if it is not there;
• remove_edge(G, x, y): removes the edge from the vertex x to the vertex y, if it is there;
• get_vertex_value(G, x): returns the value associated with the vertex x;
• set_vertex_value(G, x, v): sets the value associated with the vertex x to v.

Structures that associate values to the edges usually also provide:

• get_edge_value(G, x, y): returns the value associated with the edge (x, y);
• set_edge_value(G, x, y, v): sets the value associated with the edge (x, y) to v.

Common data structures for graph representation

Adjacency list

Vertices are stored as records or objects, and every vertex stores a list of adjacent vertices. This data structure allows the storage of additional data on the vertices. Additional data can be stored if edges are also stored as objects, in which case each vertex stores its incident edges and each edge stores its incident vertices.

Adjacency matrix

A two-dimensional matrix, in which the rows represent source vertices and columns represent destination vertices. Data on edges and vertices must be stored externally. Only the cost for one edge can be stored between each pair of vertices.

Incidence matrix

A two-dimensional matrix, in which the rows represent the vertices and columns represent the edges. The entries indicate the incidence relation between the vertex at a row and edge at a column.

The following table gives the time complexity cost of performing various operations on graphs, for each of these representations, with |V| the number of vertices and |E| the number of edges. In the matrix representations, the entries encode the cost of following an edge. The cost of edges that are not present are assumed to be ∞.

	Adjacency list	Adjacency matrix	Incidence matrix
Store graph	[math]\displaystyle{ O(|V|+|E|) }[/math]	[math]\displaystyle{ O(|V|^2) }[/math]	[math]\displaystyle{ O(|V|\cdot|E|) }[/math]
Add vertex	[math]\displaystyle{ O(1) }[/math]	[math]\displaystyle{ O(|V|^2) }[/math]	[math]\displaystyle{ O(|V|\cdot|E|) }[/math]
Add edge	[math]\displaystyle{ O(1) }[/math]	[math]\displaystyle{ O(1) }[/math]	[math]\displaystyle{ O(|V|\cdot|E|) }[/math]
Remove vertex	[math]\displaystyle{ O(|E|) }[/math]	[math]\displaystyle{ O(|V|^2) }[/math]	[math]\displaystyle{ O(|V|\cdot|E|) }[/math]
Remove edge	[math]\displaystyle{ O(|V|) }[/math]	[math]\displaystyle{ O(1) }[/math]	[math]\displaystyle{ O(|V|\cdot|E|) }[/math]
Are vertices x and y adjacent (assuming that their storage positions are known)?	[math]\displaystyle{ O(|V|) }[/math]	[math]\displaystyle{ O(1) }[/math]	[math]\displaystyle{ O(|E|) }[/math]
Remarks	Slow to remove vertices and edges, because it needs to find all vertices or edges	Slow to add or remove vertices, because matrix must be resized/copied	Slow to add or remove vertices and edges, because matrix must be resized/copied

Adjacency lists are generally preferred for the representation of sparse graphs, while an adjacency matrix is preferred if the graph is dense; that is, the number of edges |E| is close to the number of vertices squared, |V|², or if one must be able to quickly look up if there is an edge connecting two vertices.

More efficient representation of adjacency sets

The time complexity of operations in the adjacency list representation can be improved by storing the sets of adjacent vertices in more efficient data structures, such as hash tables or balanced binary search trees (the latter representation requires that vertices are identified by elements of a linearly ordered set, such as integers or character strings). A representation of adjacent vertices via hash tables leads to an amortized average time complexity of [math]\displaystyle{ O(1) }[/math] to test adjacency of two given vertices and to remove an edge and an amortized average time complexity of [math]\displaystyle{ O(\deg(x)) }[/math] to remove a given vertex x of degree [math]\displaystyle{ \deg(x) }[/math]. The time complexity of the other operations and the asymptotic space requirement do not change.

Parallel representations

The parallelization of graph problems faces significant challenges: Data-driven computations, unstructured problems, poor locality and high data access to computation ratio. The graph representation used for parallel architectures plays a significant role in facing those challenges. Poorly chosen representations may unnecessarily drive up the communication cost of the algorithm, which will decrease its scalability. In the following, shared and distributed memory architectures are considered.

Shared memory

In the case of a shared memory model, the graph representations used for parallel processing are the same as in the sequential case, since parallel read-only access to the graph representation (e.g. an adjacency list) is efficient in shared memory.

Distributed memory

In the distributed memory model, the usual approach is to partition the vertex set [math]\displaystyle{ V }[/math] of the graph into [math]\displaystyle{ p }[/math] sets [math]\displaystyle{ V_0, \dots, V_{p-1} }[/math]. Here, [math]\displaystyle{ p }[/math] is the amount of available processing elements (PE). The vertex set partitions are then distributed to the PEs with matching index, additionally to the corresponding edges. Every PE has its own subgraph representation, where edges with an endpoint in another partition require special attention. For standard communication interfaces like MPI, the ID of the PE owning the other endpoint has to be identifiable. During computation in a distributed graph algorithms, passing information along these edges implies communication.

Partitioning the graph needs to be done carefully - there is a trade-off between low communication and even size partitioning But partitioning a graph is a NP-hard problem, so it is not feasible to calculate them. Instead, the following heuristics are used.

1D partitioning: Every processor gets [math]\displaystyle{ n/p }[/math] vertices and the corresponding outgoing edges. This can be understood as a row-wise or column-wise decomposition of the adjacency matrix. For algorithms operating on this representation, this requires an All-to-All communication step as well as [math]\displaystyle{ \mathcal{O}(m) }[/math] message buffer sizes, as each PE potentially has outgoing edges to every other PE.

2D partitioning: Every processor gets a submatrix of the adjacency matrix. Assume the processors are aligned in a rectangle [math]\displaystyle{ p = p_r \times p_c }[/math], where [math]\displaystyle{ p_r }[/math] and [math]\displaystyle{ p_c }[/math] are the amount of processing elements in each row and column, respectively. Then each processor gets a submatrix of the adjacency matrix of dimension [math]\displaystyle{ (n/p_r)\times(n/p_c) }[/math]. This can be visualized as a checkerboard pattern in a matrix. Therefore, each processing unit can only have outgoing edges to PEs in the same row and column. This bounds the amount of communication partners for each PE to [math]\displaystyle{ p_r + p_c - 1 }[/math] out of [math]\displaystyle{ p = p_r \times p_c }[/math] possible ones.

Compressed representations

Graphs with trillions of edges occur in machine learning, social network analysis, and other areas. Compressed graph representations have been developed to reduce I/O and memory requirements. General techniques such as Huffman coding are applicable, but the adjacency list or adjacency matrix can be processed in specific ways to increase efficiency.

Graph traversal

Breadth first search and depth first search

Breadth-first search (BFS) and depth-first search (DFS) are two closely-related approaches that are used for exploring all of the nodes in a given connected component. Both start with an arbitrary node, the "root".

See also

• Graph traversal for more information on graph walking strategies
• Graph database for graph (data structure) persistency
• Graph rewriting for rule based transformations of graphs (graph data structures)
• Graph drawing software for software, systems, and providers of systems for drawing graphs

External links

• Boost Graph Library: a powerful C++ graph library s.a. Boost (C++ libraries)
• Networkx: a Python graph library
• GraphMatcher a java program to align directed/undirected graphs.
• GraphBLAS A specification for a library interface for operations on graphs, with a particular focus on sparse graphs.