JavaScript Interview Questions
  • JavaScript Interview Questions
  • Contact
  • Introduction
  • Question 1
  • Question 2
  • Question 3
  • Question 4
  • Question 5
  • Question 6
  • Question 7
  • Question 8
  • Question 9
  • Question 10
  • Question 11
  • Question 12
  • Question 13
  • Question 14
  • Question 15
  • Question 16
  • Question 17
  • Question 18
  • Question 19
  • Question 20
  • Question 21
  • Question 22
  • Question 23
  • Question 24
  • Question 25
  • Question 26
  • Question 27
  • Question 28
  • Question 29
  • Question 30
  • Question 31
  • Question 32
  • Question 33
  • Question 34
  • Question 35
  • Question 36
  • Question 37
  • Question 38
  • Question 39
  • Question 40
  • Question 41
  • Question 42
  • Question 43
  • Question 44
  • Question 45
  • Question 46
  • Question 47
  • Question 48
  • Question 49
  • Question 50
  • Question 51
  • Question 52
  • Question 53
  • Question 54
  • Question 55
  • Question 56
  • Question 57
  • Question 58
  • Question 59
  • Question 60
  • Question 61
  • Question 62
  • Question 63
  • Question 64
  • Question 65
  • Question 66
  • Question 67
  • Question 68
  • Question 69
  • Question 70
  • Question 71
  • Question 72
  • Question 73
  • Question 74
  • Question 75
  • Question 76
  • Question 77
  • Question 78
  • Question 79
  • Question 80
  • Question 81
  • Question 82
  • Question 83
  • Question 84
  • Question 85
  • Question 86
  • Question 87
  • Question 88
  • Question 89
  • Question 90
  • Question 91
  • Question 92
  • Question 93
  • Question 94
  • Question 95
  • Question 96
  • Question 97
  • Question 98
  • Question 99
  • Question 100
  • Epilogue
Powered by GitBook
On this page
  • Question
  • Answer

Question 84

Question

What are the performance implications of using Object.freeze()?

Answer

Understanding Object.freeze():

Object.freeze() is a method that makes an object immutable. This means that:

  • You cannot add new properties to the object.

  • You cannot modify existing property values.

  • You cannot delete existing properties.

Performance Considerations:

  1. Initial Impact: When you call Object.freeze(), it traverses the entire object graph (including nested objects) and sets the "frozen" flag on each property and its descendants. This initial traversal can have a noticeable impact on performance, especially for large or deeply nested objects.

  2. Subsequent Operations: Once an object is frozen, most operations become faster because JavaScript knows it cannot change the object's structure.

    • Attempts to modify properties will result in TypeError exceptions.

    • Accessing properties remains efficient as there's no need for dynamic property checks.

  3. Trade-offs: The performance gains from freezing come at the cost of flexibility. If you ever need to modify the frozen object, you would have to create a new object and copy the data, potentially leading to more complex logic and overhead.

When to Use Object.freeze():

  • Configuration Objects: For settings that shouldn't change during runtime (e.g., API keys, database connection strings).

  • Immutable Data Structures: When you need guaranteed immutability for data integrity (e.g., in game states or financial calculations).

Best Practices:

  • Freeze Only What's Necessary: Don't freeze entire objects if only a subset needs to be immutable. Freeze individual parts or nested objects as required.

  • Consider Alternatives: Explore other techniques like const declarations and shallow copying for achieving immutability in simpler cases.

PreviousQuestion 83NextQuestion 85

Last updated 6 months ago