Empresas
Empleos
  • Sobre nosotros
  • Soluciones
    • Publicación de vacantes
      Publica tu vacante y recibe candidatos calificados en 48h.
    • Evaluación de candidatos
      500+ pruebas técnicas y psicológicas, más anti-fraude.
    • Headhunting
      Búsqueda ejecutiva a la medida de principio a fin.
    • Nómina + EOR
      Dispersión de nómina y EOR en más de 15 países de LATAM.
  • Precios
  • Empleos

0

93
Vistas
Time limit to consider as computationally expensive for using useMemo/useCallback

According to dozens of articles, including React docs, using useCallback and useMemo hooks helps prevent unnecessary re-renders.

On the other hand, these performance-optimizing hooks are not free and come at a cost. And their benefit might not always offset that cost. So that

MOST OF THE TIME YOU SHOULD NOT BOTHER OPTIMIZING UNNECESSARY RERENDERS

said Kent C. Dodds.

So there should be a tool to measure whether a function/variable is costy to compute and that cannot be relative (e.g. putting console.time() and console.timeEnd() before and after).

Is there a number as time that beyond is considered computationally heavy for most of our product users?

about 4 years ago · Juan Pablo Isaza
1 Respuestas
Responde la pregunta

0

Is there a number as time that beyond is considered computationally heavy for most of our product users

As far as I know- there is no standard definition. In most circumstances, its not required (even for calculations that seem complex - computers are crazy fast).

As a general rule of thumb, if you see/notice delays in dom changes - then is the time to start looking for performance bottlenecks

about 4 years ago · Juan Pablo Isaza Denunciar
Responde la pregunta
Encuentra empleos remotos

¡Descubre la nueva forma de encontrar empleo!

Top de empleos
Top categorías de empleo
Empresas
Publicar vacante Precios Comercial
Legal
Términos y condiciones Política de privacidad
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomiéndame algunas ofertas
Necesito ayuda