Does SET NOCOUNT ON really make that much of a performance difference

Question

In this article, the author suggests that there is material overhead associated with SET NOCOUNT ON and that \"By removing this extra overhead from the network

Answer 1

The last link in my question here: "SET NOCOUNT ON usage" refers to an article on it.

Given how trivial it is, why not leave it in and stop the client processing another resultset?

And without SET NOCOUNT ON, nHibernate can break too (mentioned in question)