Comment by Shreyansh Pandey on "What are some tips to speed up Node.js server?"

The first thing I'd usually do in such a situation is (considering I have enough logging), run a stress test to see what all routes are giving me a problem. Once that's done, I see what do the fast ones have which the slow ones don't and vice-versa.

What exactly do you mean by "huge" MongoDB operations? How is your database connected to your server instance? Is it in the same subnet? Or it's a hosted service?

For client-side caching, I'd suggest you use ETags and then use the If-None-Match header when in the request.

You need to give us a little more information on your setup for us to help you. I am more than willing to update this information if you give me some specifics about the infrastructure.

ETags are used for client side caching via HTTP, though 😉

Marco Alka, oh lord! In a hurry, I seem to have muddled the two.

Shreyansh Pandey for just local environment the DB is setuped in a different port that is the mongodb default port. The Problem with queries is that I have some queries to update the data in the mongodb and then using it to remove a data from different collections and then again update the data based on the second collection callback. Now I know its not good practice to get things going but for now I have done like that. The question for mongodb was if I changed by mongo queries with aggregates function will it help.

Shreyansh Pandey Marco Alka is serverworker good for client - side caching ? . I am using it and actually caching the whole static files other than images. is it fine?

For images, I suggest you just use the Last-Modified header. That's a safer option. When it comes to the API, I suggest using your custom server/client-side caching methods. For other things, you are better off using something like CloudFlare or AWS CloudFront. It takes care of everything for you so you don't have to add code for manually managing cache parameters.

And can you give me an example of a "complex" Mongo query?

Aniketh Saha Depends. Is it a homepage you are running? Then it should be accessible without JS and probably on older browser, too. So

is serverworker good for client - side caching ?

No. It requires JS and modern browsers. HTTP native caching is a more stable approach. However, even for web apps, you might want to use ETags as a base-line (for the times when you want to use resources outside of the application), which you can enrich with service-workers (they can work hand-in-hand for PWAs). If you are on mobile, setting an age can further enhance the experience, because then a browser won't even try to access the resource for a set amount of time, resulting in better speed on slow connections and saving a few bytes 😃

Search Hashnode