Avl tree

42
AVL Trees Adelson-Velskii and Landis

description

AVL Trees Adelson-Velskii and Landis Binary Search Tree - Best Time All BST operations are O(d), where d is tree depth minimum d is for a binary tree with N nodes What is the best case tree? What is the worst case tree? So, best case running time of BST operations is O(log N) Binary Search Tree - Worst Time Worst case running time is O(N) What happens when you Insert elements in ascending order? Insert: 2, 4, 6, 8, 10, 12 into an empty BST Problem: Lack of “balance”: compare depths of left and right subtree Unbalanced degenerate tree Balanced and unbalanced BST Approaches to balancing trees Don&#x27;t balance May end up with some nodes very deep Strict balance The tree must always be balanced perfectly Pretty good balance Only allow a little out of balance Adjust on access Self-adjusting Balancing Binary Search Trees Many algorithms exist for keeping binary search trees balanced Adelson-Velskii and Landis (AVL) trees (height-balanced trees) Splay trees and other self-adjusting trees B-trees and other multiway search trees Perfect Balance Want a complete tree after every operation tree is full except possibly in the lower right This is expensive For example, insert 2 in the tree on the left and then rebuild as a complete tree AVL - Good but not Perfect Balance AVL trees are height-balanced binary search trees Balance factor of a node height(left subtree) - height(right subtree) An AVL tree has balance factor calculated at every node For every node, heights of left and right subtree can differ by no more than 1 Store current heights in each node Height of an AVL Tree N(h) = minimum number of nodes in an AVL tree of height h. Basis N(0) = 1, N(1) = 2 Induction N(h) = N(h-1) + N(h-2) + 1 Solution (recall Fibonacci analysis) N(h) > h (  1.62) Height of an AVL Tree N(h) > h (  1.62) Suppose we have n nodes in an AVL tree of height h. n > N(h) (because N(h) was the minimum) n > h hence log n > h (relatively well balanced tree!!) h < 1.44 log2n (i.e., Find takes O(logn)) Node Heights Node Heights after Insert 7 Insert and Rotation in AVL Trees Insert operation may cause balance factor to become 2 or –2 for some node only nodes on the path from insertion point to root node have possibly changed in height So after the Insert, go back up to the root node by node, updating heights If a new balance factor is 2 or –2, adjust tree by rotation around the node Single Rotation in an AVL Tree Implementation Single Rotation Double Rotation Implement Double Rotation in two lines. Insertion in AVL Trees Insert at the leaf (as for all BST) only nodes on the path from insertion point to root node have possibly changed in height So after the Insert, go back up to the root node by node, updating heights If a new balance factor is 2 or –2, adjust tree by rotation around the node Insert in BST Insert in AVL trees Example of Insertions in an A

Transcript of Avl tree

Page 1: Avl tree

AVL Trees

Adelson-Velskii and Landis

Page 2: Avl tree

2

Binary Search Tree - Best Time

• All BST operations are O(d), where d is tree depth

• minimum d is for a binary tree with N nodes› What is the best case tree? › What is the worst case tree?

• So, best case running time of BST operations is O(log N)

Nlogd 2

Page 3: Avl tree

3

Binary Search Tree - Worst Time

• Worst case running time is O(N) › What happens when you Insert elements in

ascending order?• Insert: 2, 4, 6, 8, 10, 12 into an empty BST

› Problem: Lack of “balance”: • compare depths of left and right subtree

› Unbalanced degenerate tree

Page 4: Avl tree

4

Balanced and unbalanced BST

4

2 5

1 3

1

5

2

4

3

7

6

4

2 6

5 71 3

Is this “balanced”?

Page 5: Avl tree

5

Approaches to balancing trees

• Don't balance› May end up with some nodes very deep

• Strict balance› The tree must always be balanced perfectly

• Pretty good balance› Only allow a little out of balance

• Adjust on access› Self-adjusting

Page 6: Avl tree

6

Balancing Binary Search Trees

• Many algorithms exist for keeping binary search trees balanced› Adelson-Velskii and Landis (AVL) trees

(height-balanced trees)› Splay trees and other self-adjusting trees› B-trees and other multiway search trees

Page 7: Avl tree

7

Perfect Balance

• Want a complete tree after every operation› tree is full except possibly in the lower right

• This is expensive› For example, insert 2 in the tree on the left and

then rebuild as a complete tree

Insert 2 &complete tree

6

4 9

81 5

5

2 8

6 91 4

Page 8: Avl tree

8

AVL - Good but not Perfect Balance

• AVL trees are height-balanced binary search trees

• Balance factor of a node› height(left subtree) - height(right subtree)

• An AVL tree has balance factor calculated at every node› For every node, heights of left and right

subtree can differ by no more than 1› Store current heights in each node

Page 9: Avl tree

9

Height of an AVL Tree

• N(h) = minimum number of nodes in an AVL tree of height h.

• Basis› N(0) = 1, N(1) = 2

• Induction› N(h) = N(h-1) + N(h-2) + 1

• Solution (recall Fibonacci analysis)

› N(h) > h ( 1.62) h-1h-2

h

Page 10: Avl tree

10

Height of an AVL Tree

• N(h) > h ( 1.62)

• Suppose we have n nodes in an AVL tree of height h.› n > N(h) (because N(h) was the minimum)

› n > h hence log n > h (relatively well balanced tree!!)

› h < 1.44 log2n (i.e., Find takes O(logn))

Page 11: Avl tree

11

Node Heights

height=2 BF=1-0=1

height of node = hbalance factor = hleft-hright

empty height = -1

1

00

2

0

6

4 9

81 5

10

0 0

6

4 9

1 5

1

Tree A (AVL) Tree B (AVL)

Page 12: Avl tree

12

Node Heights after Insert 7

height of node = hbalance factor = hleft-hright

empty height = -1

2

10

3

0

6

4 9

81 5

11

0

2

0

6

4 9

1 5

1

0

7

0

7

balance factor 1-(-1) = 2

-1

Tree A (AVL) Tree B (not AVL)

Page 13: Avl tree

13

Insert and Rotation in AVL Trees

• Insert operation may cause balance factor to become 2 or –2 for some node › only nodes on the path from insertion point to

root node have possibly changed in height› So after the Insert, go back up to the root

node by node, updating heights› If a new balance factor is 2 or –2, adjust tree

by rotation around the node

Page 14: Avl tree

14

Single Rotation in an AVL Tree

2

10

2

0

6

4 9

81 5

1

0

7

0

1

0

2

0

6

4

9

8

1 5

1

0

7

Page 15: Avl tree

15

Let the node that needs rebalancing be .

There are 4 cases: Outside Cases (require single rotation) : 1. Insertion into left subtree of left child of . 2. Insertion into right subtree of right child of . Inside Cases (require double rotation) : 3. Insertion into right subtree of left child of . 4. Insertion into left subtree of right child of .

The rebalancing is performed through four separate rotation algorithms.

Insertions in AVL Trees

Page 16: Avl tree

16

AVL Insertion: Outside Case

j

k

X Y

Z

Consider a validAVL subtree

h

hh

Page 17: Avl tree

17

AVL Insertion: Outside Case

j

k

XY

Z

Inserting into Xdestroys the AVL property at node j

h

h+1 h

Page 18: Avl tree

18

AVL Insertion: Outside Case

j

k

XY

Z

Do a “right rotation”

h

h+1 h

Page 19: Avl tree

19

Single right rotation

j

k

XY

Z

Do a “right rotation”

h

h+1 h

Page 20: Avl tree

20

Outside Case Completed

AVL property has been restored!

j

k

X Y Z

“Right rotation” done!(“Left rotation” is mirror symmetric)

h

h+1

h

Page 21: Avl tree

21

AVL Insertion: Inside Case

j

k

X Y

Z

Consider a validAVL subtree

h

hh

Page 22: Avl tree

22

AVL Insertion: Inside Case

Inserting into Y destroys theAVL propertyat node j

j

k

XY

Z

Does “right rotation”restore balance?

h

h+1h

Page 23: Avl tree

23

AVL Insertion: Inside Case

jk

X

YZ

“Right rotation”does not restorebalance… now k isout of balance

hh+1

h

Page 24: Avl tree

24

AVL Insertion: Inside Case

Consider the structureof subtree Y… j

k

XY

Zh

h+1h

Page 25: Avl tree

25

AVL Insertion: Inside Case

j

k

X

V

Z

W

i

Y = node i andsubtrees V and W

h

h+1h

h or h-1

Page 26: Avl tree

26

AVL Insertion: Inside Case

j

k

X

V

Z

W

i

We will do a left-right “double rotation” . . .

h h or h-1

h

Page 27: Avl tree

27

Double rotation : first rotation

j

k

X V

ZW

i

left rotation complete

h

h or h-1

h or h-1

h

Page 28: Avl tree

28

Double rotation : second rotation

j

k

X V

ZW

i

Now do a right rotation

h

h

h or h-1

h or h-1

Page 29: Avl tree

29

X

Double rotation : second rotation

jk

X V ZW

i

right rotation complete

Balance has been restored

hh h or h-1

Page 30: Avl tree

30

Implementation

balance (1,0,-1)

key

rightleft

No need to keep the height; just the difference in height, i.e. the balance factor; this has to be modified on the path of insertion even if you don’t perform rotations

Once you have performed a rotation (single or double) you won’t need to go back up the tree

Page 31: Avl tree

31

Single Rotation

RotateFromRight(n : reference node pointer) {p : node pointer;p := n.right;n.right := p.left;p.left := n;n := p}

You also need to modify the heights or balance factors of n and p

X

Y Z

n

Insert

Page 32: Avl tree

32

Double Rotation

• Implement Double Rotation in two lines.

DoubleRotateFromRight(n : reference node pointer) {????}

n

X

V W

Z

Page 33: Avl tree

33

Insertion in AVL Trees

• Insert at the leaf (as for all BST)› only nodes on the path from insertion point to

root node have possibly changed in height› So after the Insert, go back up to the root

node by node, updating heights› If a new balance factor is 2 or –2, adjust tree

by rotation around the node

Page 34: Avl tree

34

Insert in BST

Insert(T : reference tree pointer, x : element) : integer {if T = null then T := new tree; T.data := x; return 1;//the links to

//children are nullcase T.data = x : return 0; //Duplicate do nothing T.data > x : return Insert(T.left, x); T.data < x : return Insert(T.right, x);endcase}

Page 35: Avl tree

35

Insert in AVL treesInsert(T : reference tree pointer, x : element) : {if T = null then {T := new tree; T.data := x; height := 0; return;}case T.data = x : return ; //Duplicate do nothing T.data > x : Insert(T.left, x); if ((height(T.left)- height(T.right)) = 2){ if (T.left.data > x ) then //outside case T = RotatefromLeft (T); else //inside case T = DoubleRotatefromLeft (T);} T.data < x : Insert(T.right, x); code similar to the left caseEndcase T.height := max(height(T.left),height(T.right)) +1; return;}

Page 36: Avl tree

36

Example of Insertions in an AVL Tree

1

0

2

20

10 30

25

0

35

0

Insert 5, 40

Page 37: Avl tree

37

Example of Insertions in an AVL Tree

1

0

2

20

10 30

25

1

35

0

50

20

10 30

25

1

355

40

0

0

01

2

3

Now Insert 45

Page 38: Avl tree

38

Single rotation (outside case)

2

0

3

20

10 30

25

1

35

2

50

20

10 30

25

1

405

40

0

0

0

1

2

3

45

Imbalance35 45

0 0

1

Now Insert 34

Page 39: Avl tree

39

Double rotation (inside case)

3

0

3

20

10 30

25

1

40

2

50

20

10 35

30

1

405

45

0 1

2

3

Imbalance

45

0

1

Insertion of 34

35

34

0

0

1 25 340

Page 40: Avl tree

40

AVL Tree Deletion

• Similar but more complex than insertion› Rotations and double rotations needed to

rebalance› Imbalance may propagate upward so that

many rotations may be needed.

Page 41: Avl tree

41

Arguments for AVL trees:

1. Search is O(log N) since AVL trees are always balanced.2. Insertion and deletions are also O(logn)3. The height balancing adds no more than a constant factor to the

speed of insertion.

Arguments against using AVL trees:1. Difficult to program & debug; more space for balance factor.2. Asymptotically faster but rebalancing costs time.3. Most large searches are done in database systems on disk and use

other structures (e.g. B-trees).4. May be OK to have O(N) for a single operation if total run time for

many consecutive operations is fast (e.g. Splay trees).

Pros and Cons of AVL Trees

Page 42: Avl tree

42

Double Rotation Solution

DoubleRotateFromRight(n : reference node pointer) {RotateFromLeft(n.right);RotateFromRight(n);}

X

n

V W

Z