Replying to Avatar jimbocoin 🃏

It really depends on the situation. Browser performance has a lot of facets.

I recommend using a profiler like the one built into Chrome. It’ll tell you what’s taking all the time.

Generally, in my experience, it’s not computation that’s the issue. More likely memory. If your code is making lots of small objects, iterating them and deleting, these operations tend to dominate the non-DOM time.

Avatar
hzrd149 1y ago

Using the profiler has saved me so many times.

Also your right about memory, if you create too many object you can trigger the garbage collection to run and that always has a hit on performance

Reply to this note

Please Login to reply.

Discussion

No replies yet.