Should I use classes for Nodejs Models and controller

Quoting this stackoverflow issue

However, it's important to understand that OOP is very effective for things that can be modeled naturally with it, and is very ineffective for other things (e.g., crosscutting concerns or aspects).

Models are naturally modeled into classes, but Controllers are not.

Controllers

If you use express, it make sense to code routes using functional-programming, and this is the middleware-chaining coding idiom.

You can check also Sails.js, (Sails.js is a MVC express framework) Controllers implementation are not classes, but Models are.

Instanciation

If you have one Class instance for multiple requests, you will have the possiblity to share the access of the instance's scope (this) between multiples requests.

It is cleaner to use one Class instance per request, and to not share memory/scope between your requests.

When you scale up your server (add multiple instances), all requests will be handled in parallel, so you should not share any data between different requests on same nodejs thread.

If you need to share any memory across your requests, it means that you need to put this memory into a separated database, on a separated server.

About if using classes, performance is priority.

This choice is more about readability on my point of view. There won't be much performance difference and you should take care of premature optimization.

If your code is readable it will be easy to rework, and easy to study performance bottlenecks.