They all have plus/minus. It is hard to say without knowledge of your app. You say in terms of CPU, but all have different characteristics.
We use node extensively, great overall for quick to market and i/o type operations but requires some decent design choices to make it perform and easily maintainable.
PHP is good and you see tons of very scalable sites using it. It has issues, and done poorly (like anything) it can be a real bitch to deal with.
ASP.NET is the last one I would ever use at this point (although I spent years writing large systems in it). Mostly because of cost to deploy and scaling it can be a royal pain in the ass on top of expensive. Not that it can't be done, and done big and good. Just expensive to me compared to the other options.
Rails, I don't do anything with today. Not a bad platform from my understanding, quick to market, but generally not thought of for high performance applications. But again, design probably is the biggest factor here.
Frankly if I needed all out CPU performance for say an image filter or something along those lines, I'd write that functionality in C/C++ and connect it to any one of those frameworks. At which point I'd pick the web framework that got me to market the fastest.
If you have someone else building it, make sure they pick the one they are best in, or seek them out for being the best at what they do. Don't go to an ASP.NET shop and ask them to do it in Rails because you think that is the right framework. They might be able to do it, but unless the framework is a core competency it will never be as good as it should be.