4 ms·

> Measure things. You really have no idea how slow you are unless you have data to compare against. Can you share some examples?

• austin-cheney 2y ago
  Test automation helps with this. When I wrote a test automation application I had each step output the time difference since the application started and I could look at the difference between steps to see something was taking too long. Now, keep in mind your test automation application cannot limited in performance to the thing it is testing. Nonetheless I was still able to get to about 300 tests in 8 seconds. I would also recommend a perf tool that measures performance of a given operation as number of operations per second. Also measure transmission speed. In HTTP that is easily measured as HTTP round trip, but I am bigger fan of WebSocket which requires some amount of tooling to really master. Here is something I wrote about performance measuring just before I stopped doing JS work: https://github.com/prettydiff/wisdom/blob/master/performance_frontend.md https://github.com/prettydiff/wisdom/blob/master/performance...