For this I can suggest the Microsoft's Test Manager, if you are already a Windows user. I think, the key is the test cases' correctness and portability. As Tom77 said in his comment, sometimes even a stopwatch is enough, but ensure you make notes in a table to compare them at the end, and you are testing the right functionality of the application. For a load testing for example you can even use the windows' build-in tool, the Task Manager, to monitor the processes' behavior. You may need for some performance testing types some simple tools, but they are not very complicated.

What time-requirements are necessary (response time, timed-out.

How should be the system configured for the application's optimized.

And what if it receives too many requests?.

How should the application behave if the network is working very.

how many users will use the application in the same time?.

When you design the test cases, you should take in consideration the application's requirements and non-functionalities:

For some performance testing you don't need a specific tool, only a well-designed test case set, a bunch of test suites which with some variables can be used on any type of operating system family.

Need for speed 2015 pc fshare