Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

92
Views
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 answers
Answer question

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 Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!