Yeah with that I agree, part of the requirements can definitely be what performance is required.
The way that GP comment was written though made it sound like good performance should be part of the requirements for all software, which is what I disagree with.
Not in the sense that every project needs awesome performance. But in the sense that requirements should not what performance goals are required.
So you should note down target throughput and latency for different scenarios in your requirements.
That can be as simple as saying that any user interaction should give feedback within one second. (Be that either doing what the user requested within that one second, or giving some indication that the program is working on it.)