Tag view

#performance

Cross-subject tag search for related interview cards.

Clear

Results update as you type. Press / to jump straight into search.

Tagged with performance

18 cards

JavaScript Hard Theory

Garbage collection, memory leaks, deep copy vs shallow copy, and performance pitfalls in loops and DOM updates

JavaScript uses garbage collection, but leaks still happen when references stay alive unexpectedly or when code creates unnecessary work.

  • Leaked references block collection
  • Shallow copies can share nested state
  • Repeated DOM writes and bad loops can hurt performance

Garbage collection, memory leaks, deep copy vs shallow copy, and performance pitfalls in loops and DOM updates

React Hard Theory

React performance: slow apps, unnecessary re-renders, React.memo, PureComponent, code splitting, lazy loading, Suspense, virtualization, profiling, and bundle size

React apps become slow when they re-render too much, do expensive work in render, or ship more code and DOM than needed.

  • Measure before optimizing
  • Code splitting and virtualization reduce big costs
  • Memoization helps only when it prevents meaningful work

React performance: slow apps, unnecessary re-renders, React.memo, PureComponent, code splitting, lazy loading, Suspense, virtualization, profiling, and bundle size

Django Medium Theory

select_related vs prefetch_related

select_related joins single-valued relations in SQL; prefetch_related fetches related collections in extra queries.

  • select_related for FK and O2O
  • prefetch_related for M2M and reverse FK
  • Both reduce N+1 queries

select_related vs prefetch_related