How to Improve The Speed of Your Tests - The last couple of days I’ve been trying to improve test running speed. The longer the runs took. When it got to the point that in some sections each test was taking 600–1300ms.
Today I’ve been reminded of the importance of measuring first, rather than making assumptions.
I thought I’d write a post walking through it — that way at least something useful might come out of it, if it helps someone else.
The last couple of days I’ve been trying to improve test running speed. It was fine to start with but the more tests I added, the longer the runs took. When it got to the point that in some sections each test was taking 600–1300ms, I got fed up enough to do something about it.
I suspected it was probably a database thing, but thought I might as well try some basic Node profiling first to see if there was a smoking gun that would help.
The main goal of this blog is to explain the “Architecture of Nodejs” and to know how the Nodejs works behind the scenes. Generally, most of the server-side languages, like PHP, ASP.NET, Ruby, and including Nodejs follows multi-threaded architecture. That means for each client-side request initiates a new thread or even a new process.
Looking to build dynamic, extensively featured, and full-fledged web applications? **[Hire NodeJs Developer](https://hourlydeveloper.io/hire-dedicated-node-js-developer/ "Hire NodeJs Developer")** to create a real-time, faster, and scalable...