广度优先搜索时间复杂度分析

覆盖顶点的每个相邻边的时间复杂度是,比如说,O(N),其中 N是相邻边的数目。因此,对于 V的顶点数,时间复杂度变为 O(V*N) = O(E),其中 E是图中边的总数。既然从/向队列移除和添加一个顶点是 O(1),为什么它被添加到 BFS 的整体时间复杂度作为 O(V+E)

131360 次浏览

Performing an O(1) operation L times, results to O(L) complexity. Thus, removing and adding a vertex from/to the Queue is O(1), but when you do that for V vertices, you get O(V) complexity. Therefore, O(V) + O(E) = O(V+E)

Considering the following Graph we see how the time complexity is O(|V|+|E|) but not O(V*E).

enter image description here

Adjacency List

V     E
v0:{v1,v2}
v1:{v3}
v2:{v3}
v3:{}

Operating How BFS Works Step by Step

Step1:

Adjacency lists:

V     E
v0: {v1,v2} mark, enqueue v0
v1: {v3}
v2: {v3}
v3: {}

Step2:

Adjacency lists:

V     E
v0: {v1,v2} dequeue v0;mark, enqueue v1,v2
v1: {v3}
v2: {v3}
v3: {}

Step3:

Adjacency lists:

V     E
v0: {v1,v2}
v1: {v3} dequeue v1; mark,enqueue v3
v2: {v3}
v3: {}

Step4:

Adjacency lists:

V     E
v0: {v1,v2}
v1: {v3}
v2: {v3} dequeue v2, check its adjacency list (v3 already marked)
v3: {}

Step5:

Adjacency lists:

V     E
v0: {v1,v2}
v1: {v3}
v2: {v3}
v3: {} dequeue v3; check its adjacency list

Step6:

Adjacency lists:

V     E
v0: {v1,v2} |E0|=2
v1: {v3}    |E1|=1
v2: {v3}    |E2|=1
v3: {}      |E3|=0

Total number of steps:

|V| + |E0| + |E1| + |E2| +|E3| == |V|+|E|
4  +  2   +  1   +   1  + 0   ==  4 + 4
8   ==  8

Assume an adjacency list representation, V is the number of vertices, E the number of edges.

Each vertex is enqueued and dequeued at most once.

Scanning for all adjacent vertices takes O(|E|) time, since sum of lengths of adjacency lists is |E|.

Hence The Time Complexity of BFS Gives a O(|V|+|E|) time complexity.

I hope this is helpful to anybody having trouble understanding computational time complexity for Breadth First Search a.k.a BFS.

Queue graphTraversal.add(firstVertex);
// This while loop will run V times, where V is total number of vertices in graph.
while(graphTraversal.isEmpty == false)


currentVertex = graphTraversal.getVertex();


// This while loop will run Eaj times, where Eaj is number of adjacent edges to current vertex.
while(currentVertex.hasAdjacentVertices)
graphTraversal.add(adjacentVertex);


graphTraversal.remove(currentVertex);

Time complexity is as follows:

V * (O(1) + O(Eaj) + O(1))
V + V * Eaj + V
2V + E(total number of edges in graph)
V + E

I have tried to simplify the code and complexity computation but still if you have any questions let me know.

The other answers here do a great job showing how BFS runs and how to analyze it. I wanted to revisit your original mathematical analysis to show where, specifically, your reasoning gives you a lower estimate than the true value.

Your analysis goes like this:

  • Let N be the average number of edges incident to each node (N = E / V).
  • Each node, therefore, spends O(N) time doing operations on the queue.
  • Since there are V nodes, the total runtime is the O(V) · O(N) = O(V) · O(E / V) = O(E).

You are very close to having the right estimate here. The question is where the missing V term comes from. The issue here is that, weirdly enough, you can't say that O(V) · O(E / V) = O(E).

You are totally correct that the average work per node is O(E / V). That means that the total work done asympotically is bounded from above by some multiple of E / V. If we think about what BFS is actually doing, the work done per node probably looks more like c1 + c2E / V, since there's some baseline amount of work done per node (setting up loops, checking basic conditions, etc.), which is what's accounted for by the c1 term, plus some amount of work proportional to the number of edges visited (E / V, times the work done per edge). If we multiply this by V, we get that

V · (c1 + c2E / V)

= c1V + c2E

= Θ(V + E)

What's happening here is that those lovely lower-order terms that big-O so conveniently lets us ignore are actually important here, so we can't easily discard them. So that's mathematically at least what's going on.

What's actually happening here is that no matter how many edges there are in the graph, there's some baseline amount of work you have to do for each node independently of those edges. That's the setup to do things like run the core if statements, set up local variables, etc.

I would just like to add to above answers that if we are using an adjacency matrix instead of a adjacency list, the time complexity will be O(V^2), as we will have to go through a complete row for each vertex to check which nodes are adjacent.

You are saying that total complexity should be O(V*N)=O(E). Suppose there is no edge between any pair of vertices i.e. Adj[v] is empty for all vertex v. Will BFS take a constant time in this case? Answer is no. It will take O(V) time(more accurately θ(V)). Even if Adj[v] is empty, running the line where you check Adj[v] will itself take some constant time for each vertex. So running time of BFS is O(V+E) which means O(max(V,E)).

Will the time complexity of BFS be not O(V) considering we only have to traverse the vertices in the adjacency list? Am I missing something here?


For the below graph represented using adjacency list for ex:


0 ->1->2->null
1->3->4->null
3->null
4->null


While creating the graph we have the adjacency list which is an array of linked lists. So my understanding is during traversal this array is available to us and it's enough if we only traverse all the elements of this array and mark each element as visited to not visit it twice. What am I missing here?

One of the ways that I grasped the intuition of the time complexity O ( V + E) is that when we traverse the graph (let's take BFS pseudocode in Java):

for(v:V){ // segment 1
if(!v.isVisited) {
q = new Queue<>();
q.add(v);
v.isVisited = true
while(!q.isEmpty) {
curr  = q.poll()


for(u: curr.adjacencyList ){ //Segment 2
//do some processing
u.isVisited = true
}
}
}
}

As, we can see there are two important segments 1 and 2 which determines the time complexity.

Case 1: Consider a graph with only vertices and a few edges, sparsely connected graph (100 vertices and 2 edges). In that case, the segment 1 would dominate the course of traversal. Hence making, O(V) as the time complexity as segment 1 checks all vertices in graph space once.

Therefore, T.C. = O(V) (since E is negligible).

Case 2: Consider a graph with few vertices but a complete graph (6 vertices and 15 edges) (n C 2).

Here the segment 2 will dominate as the number of edges are more and the segment 2 gets evaluated 2|E| times for an undirected graph.

T.C. of first vertex processing would be, O(1) * O(2|E|) = O(E)

The rest of the vertex will not be evaluated for the segment 1 and would just add V-1 times of processing (since they are already visited in segment 2 which is O(V).

Thus, in this case its better to say T.C. = O(E) + O(V)

So, in the worst/best case of number of edges, we have

TC(taversing) O(E) + O(V) or

= O(E+V)